git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Jeff King <peff@peff.net>
Cc: Jim Garrison <jim.garrison@nwea.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Globbing for ignored branches?
Date: Fri, 24 Jan 2014 19:32:22 +0100	[thread overview]
Message-ID: <20140124183222.GE396@x4> (raw)
In-Reply-To: <20140124182341.GB8202@sigill.intra.peff.net>

On 2014.01.24 at 13:23 -0500, Jeff King wrote:
> On Fri, Jan 24, 2014 at 06:09:09PM +0100, Markus Trippelsdorf wrote:
> 
> > > > If you mean "ignore" in some other scenario you need to be more
> > > > specific about what you want.
> > > 
> > > I want to them when I run "git pull".
> >            ignore
> 
> I assume you mean that you do not want to fetch them at all, not that
> you want to avoid merging them. The set of branches that git fetches is
> configured by the fetch "refspec" in your config file. It usually looks
> like this:
> 
>   $ git config remote.origin.fetch
>   +refs/heads/*:refs/remotes/origin/*
> 
> But you can specify a specific list of branches you want to fetch
> instead:
> 
>   $ git config --unset remote.origin.fetch
>   $ for i in master other-branch; do
>       git config --add remote.origin.fetch \
>                        +refs/heads/$i:refs/remotes/origin/$i
>     done
> 
> However, you do have to specify each branch individually. You probably
> want to say "all branches except X", and you cannot currently specify
> a negative refspec like that.

Thanks.
Yes, that was the question I wanted to ask (, sorry for not formulating
it more clearly). 
Is this "negative refspec for branches" a feature that is planned for
the future?

-- 
Markus

  reply	other threads:[~2014-01-24 18:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  9:01 Globbing for ignored branches? Markus Trippelsdorf
2014-01-24 16:37 ` Jim Garrison
2014-01-24 17:07   ` Markus Trippelsdorf
2014-01-24 17:09     ` Markus Trippelsdorf
2014-01-24 18:23       ` Jeff King
2014-01-24 18:32         ` Markus Trippelsdorf [this message]
2014-01-24 18:55           ` Jeff King
2014-01-24 20:00             ` Junio C Hamano
2014-01-24 20:33               ` Markus Trippelsdorf
2014-01-24 20:44                 ` Junio C Hamano
2014-01-24 20:52                   ` Markus Trippelsdorf
2014-01-24 20:48               ` Jeff King
2014-01-24 21:08                 ` Junio C Hamano
2014-01-25  1:34                   ` Jeff King
2014-01-25 14:15                     ` Markus Trippelsdorf
2014-01-25 17:15                       ` Markus Trippelsdorf
2014-01-25 20:02                       ` Jeff King

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=20140124183222.GE396@x4 \
    --to=markus@trippelsdorf.de \
    --cc=git@vger.kernel.org \
    --cc=jim.garrison@nwea.org \
    --cc=peff@peff.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).