From: Junio C Hamano <gitster@pobox•com>
To: David Kastrup <dak@gnu•org>
Cc: git@vger•kernel.org
Subject: Re: git branch --merged and git branch --verbose do not combine
Date: Mon, 15 Sep 2014 13:20:51 -0700 [thread overview]
Message-ID: <xmqqwq944ov0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87a960r9d2.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 15 Sep 2014 21:07:05 +0200")
David Kastrup <dak@gnu•org> writes:
> This gives the same result as
>
> git branch --verbose --merged
>
> namely _only_ listing the current branch verbosely.
Hmph. Then that is a different issue. As I never use --merged
myself, even though I use "git branch [--verbose] --no-merged pu"
quite often to check the list of topics that I received but not yet
merged anywhere in my tree, I wouldn't be entirely surprised that
the combination does not work, but with a quick glance of the code,
especially how matches_merge_filter() uses "--[no-]merged", I cannot
offhand imagine how --no-merged would work and --merged break.
next prev parent reply other threads:[~2014-09-15 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 7:52 git branch --merged and git branch --verbose do not combine David Kastrup
2014-09-15 18:06 ` Junio C Hamano
2014-09-15 19:07 ` David Kastrup
2014-09-15 20:20 ` Junio C Hamano [this message]
2014-09-18 10:49 ` [PATCH] branch: clean up commit flags after merge-filter walk 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=xmqqwq944ov0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dak@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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