git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git branch --merged and git branch --verbose do not combine

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 15, 2014, 18:06 UTC
Message-ID
<xmqq38bs92sg.fsf@gitster.dls.corp.google.com>
In-Reply-To
<87fvfutza3.fsf@fencepost.gnu.org>
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?

Previous: David KastrupNext: David Kastrup
Message 2 of 5 in “git branch --merged and git branch --verbose do not combine”
  1. David KastrupSep 14, 2014
  2. Junio C HamanoSep 15, 2014
  3. David KastrupSep 15, 2014
  4. Junio C HamanoSep 15, 2014
  5. branch: clean up commit flags after merge-filter walkJeff King, Sep 18, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.