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

git svn clone reprocessing old commits many times?

From
JGJim Garrison <jim.garrison@nwea.org>
Date
Oct 30, 2013, 18:47 UTC
Message-ID
<0C723FEB5B4E5642B25B451BA57E273041FD4F8F@S1P5DAG3C.EXCHPROD.USA.NET>
I'm trying to clone an svn repository to git in preparation for a migration to git, including all branches and tags.
The clone is taking a long time, and it looks like every time it detects a possible branch point it backs up and reprocesses a bunch of old commits.  For example:
r43224 = f308bd7765f9923143f3883a903aebf9ac70aa42 (refs/remotes/tags/etl_app_project-2.1.3@43224)
Found branch parent: (refs/remotes/tags/etl_app_project-2.1.3) f308bd7765f9923143f3883a903aebf9ac70aa42
Following parent with do_switch
Successfully followed parent
r43225 = 0beb90a63bd0abb552ac3d36c304649dc03c402f (refs/remotes/tags/etl_app_project-2.1.3)
Found possible branch point: http://svn-server:81/svn/DevJava/trunk/ETL/etl_app => http://svn-server:81/svn/DevJava/trunk/etl_app, 44876
Initializing parent: refs/remotes/trunk@44876
r1296 = 39f1370bef9b75a5848c184befa47b999d0db73a (refs/remotes/trunk@44876)
W: +empty_dir: trunk/ETL/etl_app/src
r1697 = a68b473c64a80882c7b665fb128a12dfa8e9c355 (refs/remotes/trunk@44876)
W: +empty_dir: trunk/ETL/etl_app/src/main
r1698 = e18bd0b80ed9dd398d49bff04ca9650292f2f36d (refs/remotes/trunk@44876)
I don't understand why, for each possible branch/tag, it has to go all the way back to such an old commit and start over again.
Is this normal or is something amiss?
Message 1 of 1 in “git svn clone reprocessing old commits many times?”
  1. Jim GarrisonOct 30, 2013

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.