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

Re: Excruciatingly slow git-svn imports

From
GBGeert Bosch <bosch@adacore.com>
Date
May 6, 2008, 11:23 UTC
Message-ID
<4484D251-B919-40AE-849B-1162F057550C@adacore.com>
In-Reply-To
<20080506042508.GA23465@untitled>
On May 6, 2008, at 00:25, Eric Wong wrote:
Show 17 quoted lines
> When using "svn cp" on a top-level directory, it *should*
> just show up as a single file change in the log entry.
> Something like:
>
>  A /project/branch/my-new-branch (from /project/trunk:1234)
>
> This would not take much memory at all.
> However, I've also occasionally seen stuff like this:
>
>  A /project/branch/my-new-branch
>  A /project/branch/my-new-branch/file1 (from /project/trunk/ 
> file1:1234)
>  A /project/branch/my-new-branch/file2 (from /project/trunk/ 
> file2:1234)
>  A /project/branch/my-new-branch/file3 (from /project/trunk/ 
> file3:1234)
>  .... many more files and directories along the same lines ...
This is exactly what I'm experiencing.
> This is what I suspect Geert is seeing in his repository and causing
> problems.  Perhaps something caused by cvs2svn importing those tags  
> into
> SVN originally?

Yes, most likely. BTW, the conversion from CVS to SVN took about a day on slightly slower hardware.

   -Geert
Previous: Eric WongNext: Eric Wong
Message 8 of 9 in “Excruciatingly slow git-svn imports”
  1. Geert BoschApr 24, 2008
  2. Steven GrimmApr 24, 2008
  3. Eric WongApr 29, 2008
  4. Geert BoschMay 5, 2008
  5. Eric WongMay 6, 2008
  6. Avery PennarunMay 6, 2008
  7. Eric WongMay 6, 2008
  8. Geert BoschMay 6, 2008
  9. Eric WongApr 29, 2008

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.