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

Re: Transform log message during migration svn -> git (using git-svn)

From
Andreas Heiduk <asheiduk@gmail.com>
Date
Jun 20, 2017, 18:50 UTC
Message-ID
<e7cb2b23-21ec-f124-5198-7bb72e601184@gmail.com>
In-Reply-To
<90ee80a910884e1e98fa8a5001ae850c@GTLBML3EX0005.bagmail.net>
Am 20.06.2017 um 14:32 schrieb paul.mattke@s4m.com:
Show 6 quoted lines
> Well this is a possibility, of course. Our problem is that our SVN
> repository contains about 220.000 revisions currently. As a colleague of
> mine said that the command you suggest might take about 4 seconds per
> revision, it would take about 10 days to do this for our whole repository.
> So of course it could save a lot of time generally if such operation could
> be done immediately during git-svn.

My data point is this: A "git filter branch" run with ~2000 revisions took several hours on a Windows 7 box. That number seems to be roughly the same as your number. A comparable run on a Linux box took only about 10 minutes.

So: If your benchmark was done on Windows you might do that also on Linux.
Previous: Jeff King
Message 6 of 6 in “Transform log message during migration svn -> git (using git-svn)”
  1. paul.mattke@s4m.comJun 20, 2017
  2. Lars SchneiderJun 20, 2017
  3. AW: Transform log message during migration svn -> git (using git-svn)paul.mattke@s4m.com, Jun 20, 2017
  4. Lars SchneiderJun 20, 2017
  5. Jeff KingJun 20, 2017
  6. Andreas HeidukJun 20, 2017

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.