git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: migrating Mifos from svn to git

From
Adam Monsen <haircut@gmail.com>
Date
May 5, 2010, 04:58 UTC
Message-ID
<loom.20100505T065133-348@post.gmane.org>
In-Reply-To
<20100502082503.GG92627@acme.spoerlein.net>
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!
Previous: Ulrich Spörlein
Message 3 of 3 in “migrating Mifos from svn to git”
  1. Adam MonsenMay 1, 2010
  2. Ulrich SpörleinMay 2, 2010
  3. Adam MonsenMay 5, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.