Re: [tlug] Subversion to Git Conversions

[Lars Kotthoff <lists@example.com>]

> The plan I have been experimenting with is to do a "git svn clone" of
> the appropriate bit of my svn repo into a bare repo and declare that
> the "master" for the moment. However, nobody who clones that master
> can see the tracking refs for the branches, right? So I have to create
> the branches in the "master" git repo. Then, so long as I have only
> commits from that point onward, I can maintain the svn repo in sync by
> just doing a "git svn dcommit" on a regular basis, and even continue
> to use svn checkouts (so long as they don't commit!). If I have to
> roll back after a while, we just all switch back to svn and all is
> happy. Otherwise at some point I declare the svn repo to be suitable for
> off-line archiving, and take it down.

If you're not sure about switching, it might be a better idea to keep SVN as the
"real" master in the background, and a new "public" git repository in front of
it. I.e. all the commits go to the new git repo (which has been cloned/merged
from the svn repo) and are mirrored to the old svn repo in the background
daily/commitly.

Setting the mirroring up might be a bit tricky if you have weird branches, but
if you can just clone you svn repo into git it'll be as easy as a git svn
dcommit.

The advantage of this method is that regardless of whether you decide to keep
the svn repo or move to the git repo after a while, you can do it (almost)
immediately without any further work.

Lars