On 27/09/2012 8:44 AM, Thomas Ferris Nicolaisen wrote:
> There are two aspects you need to think a lot about: The first one is
> the organizational one. Read this experience report from Etsy
> on some more ideas on what to think about (there are plenty more
> reports like this around the web). The second is the technical
> approach, meaning how do you physically get the the code and history
> out of SVN and into Git.
> In combination of these two aspects, you need to decide whether you
> want to do either or a combination of these migrations:
> 1) a gradual migration, where you migrate subprojects/teams
> one-by-one 2) a backward compatible bridge-setup (like the one I've
> documented here
> <http://www.tfnico.com/presentations/git-and-subversion>), where
> people can try out Git while still using Subversion at the same time
> 3) a complete cold-turkey migration, where people leave the office
> one day having used subversion, and the next morning everything is in
> Git (requires a *lot* of preparation, a few failed attempts, and
> pulling off an all-nighter for the final migration).
> Before you decide on a strategy, it is wise to start experimenting
> with how a migration can work. I find the best way is using git-svn,
> and just clone *something* out of the SVN repo, and see how it works.
> git svn clone [url-to-project] and off you go.
> It is possible to do a git-svn clone of the entire Subversion
> repository into a huge Git repository, and then start splitting it
> into smaller repositories using filter-branch. You could try this to
> simulate how a cold turkey migration could work.
> Once you have some experience on these strategies, you can start
> thinking about how to work the svn:externals into this. Perhaps
> git-submodules <http://git-scm.com/book/en/Git-Tools-Submodules> is a
> good fit for them, or a different tool like gitslave
> <http://gitslave.sourceforge.net/>.
> Depending on your organization, be prepared for weeks or months of
> hard work for this to come through, plus a lot of organizational
> resistance. You'll probably have to become a Git/git-svn guru on the
> way in order to pull through.
Thanks for the starting points Thomas - I am already the local SVN and
general Revision Control Gru, (not so much an expert as the only one who
knows anything/thinks about it/RTFM.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to