Are you already in love with Git? I’m pretty sure of that, that’s the reason why you are reading this, huh?
These are the steps you should follow to migrate an existing SVN repository to a Git one:
1 – Create a file where you will map SVN users to Git users, following this pattern:
svn_user = git_user
This is the one I created to migrate some SVN repositories from Google Code:
In a previous post, we have seen what Git is and its main characteristics. Now, we’ll go more into detail about its functionality and we’ll see what a usual day working with Git looks like.
But before, some initial concepts:
Repository: A working tree of files and directories which can be versioned, keeping track of every single modification made over the working tree, been able to move forward and backward in its history.
One of the key tools of a software project development is the repository where it’s hosted. During my experience as software developer I have been working with several flavors, such as Visual SourceSafe, CVS, Mercurial, and of course, SVN. But latetly I have found this little jewel called Git.
Git was initially developed by Linus Torvalds as a result of an unsuccessful research to replace the propietary SCM BitKeeper, used back in 2005 in the Linux Kernel project (kinda strange that the opensource star project was hosted with a propietary software, huh?
