From: Jed Brown <jed@59a2.org>
Date: Sat, 23 Mar 2013 02:46:42 GMT
Subject: Re: git branch: multiple --merged and --no-merged options?
Message-ID: <8738vmu92l.fsf@59A2.org>
In-Reply-To: <20130322175034.GB29011@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> On Fri, Mar 15, 2013 at 02:38:12PM -0500, Jed Brown wrote:
>>   $ git branch --no-merged master --merged next
>
> Yeah, sadly that does not work, as we use the same slot for the flag and
> store only one of the two (and we also allow only one "--merged" head,
> even though you could in theory want to know "merged to X, or merged to
> Y").

Hmm, I would have said conjunction (AND) was more natural than
disjunction (OR). If we add support for multiple '--merged' and
'--no-merged', do we expect to eventually have a full query grammar?