From: Jakub Narebski <jnareb@gmail.com>
Date: Tue, 20 Mar 2007 23:30:46 GMT
Subject: Re: GIT v1.5.1-rc1
Message-ID: <etpqlk$jvq$1@sea.gmane.org>
In-Reply-To: <20070320144206.GB1750@spearce.org>

Shawn O. Pearce wrote:

> Andy Parkins <andyparkins@gmail.com> wrote:
>> On Tuesday 2007 March 20 02:55, Shawn O. Pearce wrote:
>>> think they are stuck on the fact that you cannot use:
>>>
>>>     git log $new --not --all
>> 
>>> That almost needs a --all-except="refs/heads/a refs/heads/b" option
>>> to rev-list.  Grrrr.
>> 
>> I'm afraid so.  Would a --ignore list be more appropriate?  That way you could 
>> list any refs you wanted (i.e. not just --all) and then have that list 
>> finally filtered by --ignore.
> 
> Last night on #git Dscho suggested something like:
> 
>   git log $new --not '!a' '!b' --all
> 
> as a way to say ignore ref a and ref b when otherwise parsing the
> command line arguments.  Ugly, very ugly.  But is more or less the
> same idea you are talking about with the --ignore flag.

You mean

  git log $new --not ^a ^b --all

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git