On 18:14 Wed 09 Mar , John Kristian wrote: Mr Kristian: > Thanks for sharing your experience. After patching git-svn, were you able to clone your subversion repository? Indeed I was, it took about 48 hours to to the initial import. However, I forgot to mention one other important thing that was a problem. There is a pattern in svn of doing the following: /trunk/module1 /trunk/module2 /trunk/module3 Then some branches will be like this: svn cp /trunk/ /branches/mybranch1 and others might be: svn cp /trunk/module2 /brancyes/mybranchofmodule2 If this hasn't ever been done on your repository, you can stop reading now. There is no way to represent this in Git directly, so the correct thing to do here is to create a git repository for each module. Now the hard thing is telling git-svn how to handle this. I ended up writing a python script that reads in the SVN changelog and finds all of the children of e.g. /trunk/module1. Any that were copied from /trunk, it appends "/module1" to the path, and any that were copied from /trunk/module1, it leaves alone. This then goes in the git configuration file as the list of branches to fetch. -Jason -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html