From: Eric Wong <normalperson@yhbt•net>
To: Daniele Segato <daniele.bilug@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: how to skip branches on git svn clone/fetch when there are errors
Date: Sat, 5 Sep 2009 18:48:38 -0700 [thread overview]
Message-ID: <20090906014837.GD28829@dcvr.yhbt.net> (raw)
In-Reply-To: <1252140904.8992.6.camel@localhost>
Daniele Segato <daniele.bilug@gmail•com> wrote:
> Il giorno ven, 04/09/2009 alle 23.16 -0700, Eric Wong ha scritto:
> > It's unfortunate, but there's not yet an exclude/ignore directive
> > when globbing. You'll have to change your $GIT_CONFIG to only
> > have a list of branches you want, something like this:
> >
> > [svn-remote "svn"]
> > url = svn://svn.mydomain.com
> > fetch = path/to/repo/HEAD/root:refs/remotes/svn/trunk
> >
> > ; have one "fetch" line for every branch except the one you want
> > fetch = path/to/repo/BRANCHES/a/root:refs/remotes/svn/a
> > fetch = path/to/repo/BRANCHES/b/root:refs/remotes/svn/b
> > fetch = path/to/repo/BRANCHES/c/root:refs/remotes/svn/c
> >
> > ; you can do the same for tags if you have the same problem
> > tags = path/to/repo/TAGS/*/root:refs/remotes/svn/tags/*
> >
> > But you shouldn't have to worry about having "fetch" entries for
> > stale/old branches/tags you've already imported.
>
> I see...
> That means that then I'll have to manually add new created branches,
> right?
Yes.
--
Eric Wong
next prev parent reply other threads:[~2009-09-06 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 8:26 how to skip branches on git svn clone/fetch when there are errors Daniele Segato
2009-09-05 6:16 ` Eric Wong
2009-09-05 8:55 ` Daniele Segato
2009-09-06 1:48 ` Eric Wong [this message]
2009-09-07 9:30 ` Daniele Segato
2009-09-07 13:34 ` Daniele Segato
2009-09-07 13:53 ` Daniele Segato
2009-09-07 15:53 ` Paolo Ciarrocchi
2009-09-07 17:55 ` Daniele Segato
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=20090906014837.GD28829@dcvr.yhbt.net \
--to=normalperson@yhbt$(echo .)net \
--cc=daniele.bilug@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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