Your problem sounds to me like the use case for git-svn:
- set up your Git repo:
git svn clone http://svn.example.com/project/trunk - while being online, commit your changes to SVN
- before going offline, do a
git svn rebaseto get your Git repo in sync with the SVN repo - while being offline, commit to the Git repo using
git commit - when getting back online again, do a
git svn dcommitto push your changes back to the SVN repo
I’m using this workflow daily!
You get two huge advantages doing so:
- your complete SVN history is backed up in the Git repo and in every Git repo that gets cloned from that one
- while being offline, you can view the commit messages, checkout other branches, etc.