From: David Kastrup <dak@gnu•org>
To: git@vger•kernel.org
Subject: git branch --merged and git branch --verbose do not combine
Date: Sun, 14 Sep 2014 09:52:04 +0200 [thread overview]
Message-ID: <87fvfutza3.fsf@fencepost.gnu.org> (raw)
dak@lola:/usr/local/tmp/lilypond$ ../git/git branch --merged --verbose
fatal: malformed object name --verbose
dak@lola:/usr/local/tmp/lilypond$ ../git/git branch --verbose --merged
* (detached from 5b2267a) 1c23f39 Merge branch 'issue4097' into HEAD
issue346 8cf033e Issue 346: monochord issues
dak@lola:/usr/local/tmp/lilypond$ ../git/git branch --merged
* (detached from 5b2267a)
issue346
issue3855
issue4030
issue4083
issue4092
issue4096
issue4097
removelyr
test-master
test-staging
So depending on the order of --verbose and --merged, one gets an
incomplete list (basically ignoring --merged) or an error message.
Since both behavior and naming of the --verbose option is more or less
orthogonal to other listing options, it would make sense to allow it to
combine with them.
--
David Kastrup
next reply other threads:[~2014-09-14 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 7:52 David Kastrup [this message]
2014-09-15 18:06 ` git branch --merged and git branch --verbose do not combine Junio C Hamano
2014-09-15 19:07 ` David Kastrup
2014-09-15 20:20 ` Junio C Hamano
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=87fvfutza3.fsf@fencepost.gnu.org \
--to=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