# New converstion tool: svn2git.py 4 messages from 2008-11-19 to 2008-11-20. Participants: Neil Schemenauer, Kevin Menard, Daniel Barkalow. Thread: https://gitlist.dev/t/16399 ## Neil Schemenauer, 2008-11-19 19:13 Subject: New converstion tool: svn2git.py Message-ID: <20081119191320.GA20870@arctrix.com> URL: https://gitlist.dev/e/20081119191320.GA20870%40arctrix.com ``` Hi, I'm working on a tool to do conversions from SVN to git using a SVN dump. It's in early development but perhaps some people would be interested in it: http://python.ca/nas/python/svn2git.py I would like to improve it so that it intelligently converts SVN branches and tags into git branches (when possible). The basic idea is to map SVN paths into git branches, e.g. trunk -> master, branches/foo -> branch-foo, tags/bar -> tags-bar. Next, specific SVN dump actions like: Node-path: branches/foo Node-kind: dir Node-action: add Node-copyfrom-rev: 3 Node-copyfrom-path: trunk need to be detected and the commit needs to performed with the correct parent. One complication is that SVN can create a branch or tag from anywhere, for example, the action Node-path: tags/bar Node-kind: dir Node-action: add Node-copyfrom-rev: 3 Node-copyfrom-path: trunk/subdir would create tags/bar based on revision 3 of trunk/subdir. There doesn't seem to be a good way to convert that into git. I was thinking that the tags-bar branch in that case would have no parent. Would git still efficently pack that or would you end up with extra blobs? Neil ``` ## Kevin Menard, 2008-11-19 19:39 Subject: Re: New converstion tool: svn2git.py Message-ID: <7e3605160811191139t34c5de7q1912475f778386e8@mail.gmail.com> URL: https://gitlist.dev/e/7e3605160811191139t34c5de7q1912475f778386e8%40mail.gmail.com In-Reply-To: <20081119191320.GA20870@arctrix.com> ``` Hi Neil, You may want to look at this Ruby implementation for more ideas: http://github.com/nirvdrum/svn2git/ I forked it from a project originally by James Coglan, but should be able to answer most questions about it. -- Kevin On Wed, Nov 19, 2008 at 2:13 PM, Neil Schemenauer wrote: > Hi, > > I'm working on a tool to do conversions from SVN to git using a SVN > dump. It's in early development but perhaps some people would be > interested in it: > > http://python.ca/nas/python/svn2git.py > > I would like to improve it so that it intelligently converts SVN > branches and tags into git branches (when possible). The basic idea > is to map SVN paths into git branches, e.g. trunk -> master, > branches/foo -> branch-foo, tags/bar -> tags-bar. Next, specific > SVN dump actions like: > > Node-path: branches/foo > Node-kind: dir > Node-action: add > Node-copyfrom-rev: 3 > Node-copyfrom-path: trunk > > need to be detected and the commit needs to performed with the > correct parent. One complication is that SVN can create a branch or > tag from anywhere, for example, the action > > Node-path: tags/bar > Node-kind: dir > Node-action: add > Node-copyfrom-rev: 3 > Node-copyfrom-path: trunk/subdir > > would create tags/bar based on revision 3 of trunk/subdir. There > doesn't seem to be a good way to convert that into git. I was > thinking that the tags-bar branch in that case would have no parent. > Would git still efficently pack that or would you end up with extra > blobs? > > Neil > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ``` ## Neil Schemenauer, 2008-11-19 20:40 Subject: Re: New converstion tool: svn2git.py Message-ID: <20081119204032.GA21441@arctrix.com> URL: https://gitlist.dev/e/20081119204032.GA21441%40arctrix.com In-Reply-To: <7e3605160811191139t34c5de7q1912475f778386e8@mail.gmail.com> ``` On Wed, Nov 19, 2008 at 02:39:26PM -0500, Kevin Menard wrote: > You may want to look at this Ruby implementation for more ideas: > > http://github.com/nirvdrum/svn2git/ > Hi Kevin, Thanks for the link. I see that git-svn does most of the heavy lifting and now I see that it does try to intelligently handle branches and tags by looking for a suitable parent commit. I will have to look closer at what it's doing. Maybe it is sufficient for my task. Regards, Neil ``` ## Daniel Barkalow, 2008-11-20 18:49 Subject: Re: New converstion tool: svn2git.py Message-ID: URL: https://gitlist.dev/e/alpine.LNX.1.00.0811201329460.19665%40iabervon.org In-Reply-To: <20081119191320.GA20870@arctrix.com> ``` On Wed, 19 Nov 2008, Neil Schemenauer wrote: > Hi, > > I'm working on a tool to do conversions from SVN to git using a SVN > dump. It's in early development but perhaps some people would be > interested in it: > > http://python.ca/nas/python/svn2git.py > > I would like to improve it so that it intelligently converts SVN > branches and tags into git branches (when possible). The basic idea > is to map SVN paths into git branches, e.g. trunk -> master, > branches/foo -> branch-foo, tags/bar -> tags-bar. Next, specific > SVN dump actions like: > > Node-path: branches/foo > Node-kind: dir > Node-action: add > Node-copyfrom-rev: 3 > Node-copyfrom-path: trunk > > need to be detected and the commit needs to performed with the > correct parent. One complication is that SVN can create a branch or > tag from anywhere, for example, the action > > Node-path: tags/bar > Node-kind: dir > Node-action: add > Node-copyfrom-rev: 3 > Node-copyfrom-path: trunk/subdir > > would create tags/bar based on revision 3 of trunk/subdir. There > doesn't seem to be a good way to convert that into git. I was > thinking that the tags-bar branch in that case would have no parent. Probably the best thing in git would be to have the parent of the initial commit on that branch be revision 3 of trunk; it will look like a big rename of everything from subdir/* into the project root directory, which is essentially what happened. > Would git still efficently pack that or would you end up with extra > blobs? git will only ever store a single copy of identical file contents, regardless of anything at all. Furthermore, when making a pack, git compresses everything in the pack against everything else in the pack. Its heuristics also ignore the leading directory names in guessing which blobs are likely to help in compression (because there's a good chance that anything named "Makefile" anywhere is useful in compressing anything else named "Makefile"). -Daniel *This .sig left intentionally blank* ```