From: Jed Brown <jed@59A2.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git branch: multiple --merged and --no-merged options?
Date: Fri, 22 Mar 2013 21:46:42 -0500 [thread overview]
Message-ID: <8738vmu92l.fsf@59A2.org> (raw)
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?
next prev parent reply other threads:[~2013-03-23 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:38 git branch: multiple --merged and --no-merged options? Jed Brown
2013-03-22 17:50 ` Jeff King
2013-03-23 2:46 ` Jed Brown [this message]
2013-03-23 8:13 ` 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=8738vmu92l.fsf@59A2.org \
--to=jed@59a2.org \
--cc=git@vger.kernel.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).