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

Re: Start git svn clone at specific revision for cloning subprojects in large svn repositories?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Oct 22, 2008, 15:08 UTC
Message-ID
<48FF41FB.4080403@drmicha.warpmail.net>
In-Reply-To
<pan.2008.10.22.15.00.21.403423@yahoo.com>
Jeff Kowalczyk venit, vidit, dixit 10/22/08 17:00:
Show 10 quoted lines
> I would like to git svn clone subprojects from a large community
> subversion repository (plone collective).
> 
> The repository is currently at 74K commits, but subprojects of interest
> are typically much more recent, and their initial import revision is known.
> 
> I would like to avoid a) unnecessary traffic to the svn server and b)
> the very long delay in git svn cloning these subprojects.
> 
> Is there a way to specfiy a starting revision to git svn clone?
Your friendly man page provider says:
       -r <ARG>, --revision <ARG>
           Used with the fetch command.
           This allows revision ranges for partial/cauterized history to
be supported. $NUMBER, $NUMBER1:$NUMBER2 (numeric
           ranges), $NUMBER:HEAD, and BASE:$NUMBER are all supported.
           This can allow you to make partial mirrors when running
fetch; but is generally not recommended because history
           will be skipped and lost.
Usage of "Scroll Down" is strongly advised when viewing git help svn ;)
Michael

P.S.: It works nicely, don't mind the warning in the man page if you know the start rev for sure.

Previous: Jacob Helwig
Message 3 of 3 in “Start git svn clone at specific revision for cloning subprojects in large svn repositories?”
  1. Jeff KowalczykOct 22, 2008
  2. Jacob HelwigOct 22, 2008
  3. Michael J GruberOct 22, 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.