From: Johannes Sixt <j.sixt@viscovery.net>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: 'git branch --no-merge' is ambiguous
Date: Fri, 25 Sep 2009 12:28:57 +0200 [thread overview]
Message-ID: <4ABC9B69.5010205@viscovery.net> (raw)
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 reply other threads:[~2009-09-25 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 10:28 Johannes Sixt [this message]
2009-09-25 18:44 ` 'git branch --no-merge' is ambiguous Andreas Schwab
2009-09-27 7:33 ` Jeff King
2009-09-27 8:01 ` Andreas Schwab
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=4ABC9B69.5010205@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.