Ulrich Spörlein writes: > svn2git is faster and can cope with multiple branches better, but it has > bugs of its own. Try both of them ... I did, and--maybe since svn2git appears to be built atop git-svn--they both break at the same point, spouting an error like: fatal: ambiguous argument '2f53ad77827c0f1d492c031be4fff20b0d60fffc ^..1a6f5af6bd84cb71f25fb1df1c67de1a9b91ba87': unknown revision or path not in the working tree. Use '--' to separate paths from revisions rev-list 2f53ad77827c0f1d492c031be4fff20b0d60fffc ^..1a6f5af6bd84cb71f25fb1df1c67de1a9b91ba87: command returned error: 128 Anyway, I gave up trying to import all svn 1.5+ mergeinfo. Instead, I'm just pulling in our trunk into one repository, and two release branches into separate repositories. Here's my in-progress experiment so far: http://mifos.git.sourceforge.net/git/gitweb-index.cgi . "head" is what used to be "trunk" in svn. I started writing up a procedure for our developers here: http://www.mifos.org/developers/wiki/MifosVersionControlGuide If anyone wants to perfect that wiki page, I would love the help. > Yes, if both repos have the same UUID this should be possible. You need > to fudge this in rev 0 and uuid in your svn mirror. This is helpful. Thank you! -- 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