From: Michael Hendricks <michael@ndrix.org>
To: git@vger.kernel.org
Subject: Re: git-svn: importing branches later
Date: Tue, 8 May 2007 09:34:29 -0600 [thread overview]
Message-ID: <20070508153428.GB5349@ginosko.local> (raw)
In-Reply-To: <m2odkv2wtd.fsf@ziti.local>
On Tue, May 08, 2007 at 07:51:10AM -0700, Seth Falcon wrote:
> Karl Hasselström <kha@treskal.com> writes:
>
> > On 2007-05-07 13:07:06 -0600, Michael Hendricks wrote:
> >
> >> Now I want to import the 'foo' branch from the same SVN repo without
> >> grabbing all the branches. Any suggestions?
> >
> > I seem to recall that just adding another "fetch" line to the git-svn
> > configuration in .git/config will do this for you.
>
> Yes, this should work. As long as you started out with a fairly
> recent git (sorry, I don't know how recent is needed) you should have
> in your repository a git/config file containing something like:
>
> [svn-remote "svn"]
> url = http://main.svn.url.com/
> fetch = trunk:refs/remotes/git-svn
> fetch = branches/b1:refs/remotes/b1 <-- this line added by you
Thanks Seth and Karl, that does indeed work.
I noticed that after changing .git/config and running fetch, git-svn
retrieves the log for the entire project (presumably because it doesn't
know when the new branch was created). In one project with ~30,000
revisions, I found it beneficial to specify "git svn fetch -r
12345:HEAD" where revision 12345 is somewhere close to and before the
point at which the new branch was created from trunk. That makes the
initial fetch must faster.
--
Michael
prev parent reply other threads:[~2007-05-08 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 19:07 git-svn: importing branches later Michael Hendricks
2007-05-08 8:51 ` Karl Hasselström
2007-05-08 14:51 ` Seth Falcon
2007-05-08 15:34 ` Michael Hendricks [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=20070508153428.GB5349@ginosko.local \
--to=michael@ndrix.org \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).