git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Anatoly Borodin <anatoly.borodin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug? Short command line options
Date: Fri, 23 Sep 2016 00:47:57 -0400	[thread overview]
Message-ID: <20160923044757.7pwwzkqzkb2fqa7l@sigill.intra.peff.net> (raw)
In-Reply-To: <ns19t4$s0t$1@blaine.gmane.org>

On Thu, Sep 22, 2016 at 07:03:00PM +0000, Anatoly Borodin wrote:

> is there a good reason why
> 
> 	git fetch -vpnf
> 
> works like
> 
> 	git fetch -v -p -n -f
> 
> and
> 	
> 	git commit -avem msg
> 
> works like
> 
> 	git commit -a -v -e -m msg
> 
> etc etc, but
> 
> 	git log -wWp
> 
> says
> 
> 	fatal: unrecognized argument: -wWp

Yes. The reason is that the arguments to git-log are passed to the
revision.c parser, which predates our parse_options() infrastructure,
and does not understand bundled options.

It could be updated to use parse_options(), but nobody has done so yet.

-Peff

      reply	other threads:[~2016-09-23  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 19:03 Bug? Short command line options Anatoly Borodin
2016-09-23  4:47 ` Jeff King [this message]

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=20160923044757.7pwwzkqzkb2fqa7l@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=anatoly.borodin@gmail.com \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).