From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff Kowalczyk <jtk@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Start git svn clone at specific revision for cloning subprojects in large svn repositories?
Date: Wed, 22 Oct 2008 17:08:43 +0200 [thread overview]
Message-ID: <48FF41FB.4080403@drmicha.warpmail.net> (raw)
In-Reply-To: <pan.2008.10.22.15.00.21.403423@yahoo.com>
Jeff Kowalczyk venit, vidit, dixit 10/22/08 17:00:
> 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.
prev parent reply other threads:[~2008-10-22 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 15:00 Start git svn clone at specific revision for cloning subprojects in large svn repositories? Jeff Kowalczyk
2008-10-22 15:07 ` Jacob Helwig
2008-10-22 15:08 ` Michael J Gruber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48FF41FB.4080403@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jtk@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.