Yes, I know. Why would you want to migrate from Git to SVN?
Well I happen to be in a situation that I need to migrate a huge Git repo to Subversion! Here’s one workflow I tried per Edwin’s comment:
first create a local SVN repo:
svnadmin create svn_repo
Next I check out my Git repo:
git clone git:myNameSpace/myProject
cd into the myProject and run:
git svn init -s --prefix=svn/ file:///home/myHome/svn_repo/myProject
git svn fetch
git rev-list --parents master | grep '^.\{40\}$' to look up the hash of your root commit and gives only one commit as it should.
Next is to get the hash of the empty trunk commit:
git rev-parse svn/trunk
This one unfortunately fails with:
fatal: ambiguous argument 'svn/trunk': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
Well I can’t go much after this….
I would recommend you to migrate that with SubGit in several easy steps.
That’s all. While translation SubGit will try to preserve all commits (even temporary), branches, merges, ignores, dates, EOLs settings, tags and so on, as it it possible.
After translation the repositories will be in sync (each push to Git is translated to SVN revision and vice versa). To break synchronization (if you don’t need it) run