On 2014.01.24 at 20:34 -0500, Jeff King wrote:
On Fri, Jan 24, 2014 at 01:08:42PM -0800, Junio C Hamano wrote:
Not really. You do not have to view it as 'not refs/heads/foo' is
affecting the previous '+refs/heads/*:refs/remotes/origin/*'.
You can think of two refspecs refs/heads/foo
On 2014.01.25 at 15:15 +0100, Markus Trippelsdorf wrote:
On 2014.01.24 at 20:34 -0500, Jeff King wrote:
On Fri, Jan 24, 2014 at 01:08:42PM -0800, Junio C Hamano wrote:
Not really. You do not have to view it as 'not refs/heads/foo' is
affecting the previous
On Sat, Jan 25, 2014 at 03:15:42PM +0100, Markus Trippelsdorf wrote:
Many thanks for the patch. It seems to work as advertised, but only if
the negative refspec appears on a separate line. For example:
[remote origin]
url = git://gcc.gnu.org/git/gcc.git
fetch =
-Original Message-
Behalf Of Markus Trippelsdorf
Sent: Friday, January 24, 2014 1:01 AM
Subject: Globbing for ignored branches?
I would like to ignore branches that match a certain pattern, e.g.:
[snip]
Is it possible to ignore all branches that match hjl?
If you mean ignore
On 2014.01.24 at 18:07 +0100, Markus Trippelsdorf wrote:
On 2014.01.24 at 16:37 +, Jim Garrison wrote:
-Original Message-
Behalf Of Markus Trippelsdorf
Sent: Friday, January 24, 2014 1:01 AM
Subject: Globbing for ignored branches?
I would like to ignore branches
On 2014.01.24 at 16:37 +, Jim Garrison wrote:
-Original Message-
Behalf Of Markus Trippelsdorf
Sent: Friday, January 24, 2014 1:01 AM
Subject: Globbing for ignored branches?
I would like to ignore branches that match a certain pattern, e.g.:
[snip]
Is it possible to
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
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
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
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.
Yes, that was the question I wanted to ask (,
Jeff King p...@peff.net writes:
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
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.
Yes, that was
On 2014.01.24 at 12:00 -0800, Junio C Hamano wrote:
Jeff King p...@peff.net writes:
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
However, you do have to specify each branch individually. You probably
want to say all branches except X, and you cannot currently
Markus Trippelsdorf mar...@trippelsdorf.de writes:
On 2014.01.24 at 12:00 -0800, Junio C Hamano wrote:
Jeff King p...@peff.net writes:
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
However, you do have to specify each branch individually. You probably
want to
On Fri, Jan 24, 2014 at 12:00:16PM -0800, Junio C Hamano wrote:
Jeff King p...@peff.net writes:
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
However, you do have to specify each branch individually. You probably
want to say all branches except X, and you
On 2014.01.24 at 12:44 -0800, Junio C Hamano wrote:
Markus Trippelsdorf mar...@trippelsdorf.de writes:
On 2014.01.24 at 12:00 -0800, Junio C Hamano wrote:
Jeff King p...@peff.net writes:
On Fri, Jan 24, 2014 at 07:32:22PM +0100, Markus Trippelsdorf wrote:
However, you do have
Jeff King p...@peff.net writes:
I had imagined a not token at the front of the refspec, like:
git fetch origin +refs/heads/*:refs/remotes/origin/* ^refs/heads/foo
In this case, a colon in the refspec would be an error. An alternative
would be:
git fetch origin
On Fri, Jan 24, 2014 at 01:08:42PM -0800, Junio C Hamano wrote:
Not really. You do not have to view it as 'not refs/heads/foo' is
affecting the previous '+refs/heads/*:refs/remotes/origin/*'.
You can think of two refspecs refs/heads/foo refs/heads/bar are
both affecting the end result; so
16 matches
Mail list logo
