![]() ![]() Step Two: Create the new Git repository and run the conversion.Ĭreate a directory of the new Git repository: mkdir Some-Project Save that svn-authors.txt and move onto the next steps. Here is how you would do this.įirst, in the Subversion cloned directory, run this command to get a list of authors connected to the Subversion repository: svn log -xml | grep author | sort -u | perl -pe 's/.*>(.*?) While the Subversion repository to Git repository process is pretty clean, the one thing you need to do before you start is to map the user names from the Subversion repository to something that matches users in the Git repository. Step 1: Prepare the Subversion author list map file for Git usage. Checkout the trunk branch in the converted Git repo.Convert the Subversion repo to a Git repo.Map the authors from Subversion to Git format.Here is how I use it: There are two initial major steps and one after-conversion step: It uses git-svn to clone an svn repository and does some clean-up to make sure branches and tags are imported in a meaningful way, and that the code checked into master ends up being what's currently in your svn trunk rather than whichever svn branch your last commit was in.” “ svn2git is a tiny utility for migrating projects from Subversion to Git while keeping the trunk, branches and tags where they should be. Nope… Yes you can! Just use the snv2git Ruby GEM: “I don't think there is a way to convert the subversion information into Git information.” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |