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 11:06:23 -0700 [thread overview]
Message-ID: <xmqq38bs92sg.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87fvfutza3.fsf@fencepost.gnu.org> (David Kastrup's message of "Sun, 14 Sep 2014 09:52:04 +0200")
David Kastrup <dak@gnu•org> writes:
> dak@lola:/usr/local/tmp/lilypond$ ../git/git branch --merged --verbose
> fatal: malformed object name --verbose
Only at the very end of the command line if you omit something that
is required, Git helps by defaulting the missing rev to HEAD. You
can be a bit more explicit in the middle, i.e. instead of asking
"Which are branches that already has been merged in --verbose?", you
can ask "branch --merged HEAD --verbose", meaning "What are branhes
that already has been merged in HEAD, please give me a verbose
answer?" perhaps?
next prev parent reply other threads:[~2014-09-15 18:06 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 [this message]
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=xmqq38bs92sg.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