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

'git branch --no-merge' is ambiguous

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Sep 25, 2009, 10:28 UTC
Message-ID
<4ABC9B69.5010205@viscovery.net>
Look here:
 $ git branch --merge
 * master
 $ git branch --no-merge
 error: Ambiguous option: no-merge (could be --no-merged or --no-merged)
 usage: ...
     --no-merged <commit>  print only not merged branches
     --merged <commit>     print only merged branches

I tried to debug it, but parse_long_opt() is such awful spaghetti code that I don't grok it. Please help.

-- Hannes
Next: Andreas Schwab
Message 1 of 4 in “'git branch --no-merge' is ambiguous”
  1. Johannes SixtSep 25, 2009
  2. Andreas SchwabSep 25, 2009
  3. Jeff KingSep 27, 2009
  4. Andreas SchwabSep 27, 2009

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.