From: Daniele Segato <daniele.bilug@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
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, 05 Sep 2009 10:55:04 +0200 [thread overview]
Message-ID: <1252140904.8992.6.camel@localhost> (raw)
In-Reply-To: <20090905061657.GC22272@dcvr.yhbt.net>
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?
well... I tried to avoid this kind of configuration for weeks :) but
that's probably my best way with that repo....
thank you,
Daniele
next prev parent reply other threads:[~2009-09-05 8:55 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 [this message]
2009-09-06 1:48 ` Eric Wong
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=1252140904.8992.6.camel@localhost \
--to=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).