I used git-svn to save the βupdateβ from the remote repository, but did not use it to commit to the svn repository, so I cannot help you with this part.
What you do is simple, with all the default settings:
>git svn init <url......> >git svn fetch
When you do this, it pulls it into the "remote" branch called "git-svn". To combine it with the current branch:
>git merge git-svn
You may encounter some problems if you use git-svn after the fact. I mean: you already have the project checked with svn, and then you created the git repository in the local svn working directory. Then you use git-svn on top of this.
Two questions I had to deal with:
Line endings. svn can convert line endings to windows, and git-svn save them in unix style. This way you can get tons of conflicts due to the difference ending in a line.
Thus, use a tool to convert line endings for all files to unix (or depending on which line ends in svn repo).
The svn keyword extension. e.g. $Id$
git-svn will not extend these keywords, but svn will not. This way you will also have conflicts. Again, use a tool (or write a script) that converts all instances of $Id .......crap.....$ only to $ Id $ `
hasen source share