* Bug? Short command line options
@ 2016-09-22 19:03 Anatoly Borodin
2016-09-23 4:47 ` Jeff King
0 siblings, 1 reply; 2+ messages in thread
From: Anatoly Borodin @ 2016-09-22 19:03 UTC (permalink / raw)
To: git
Hi All,
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
?
--
Mit freundlichen Grüßen,
Anatoly Borodin
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug? Short command line options
2016-09-22 19:03 Bug? Short command line options Anatoly Borodin
@ 2016-09-23 4:47 ` Jeff King
0 siblings, 0 replies; 2+ messages in thread
From: Jeff King @ 2016-09-23 4:47 UTC (permalink / raw)
To: Anatoly Borodin; +Cc: git
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-09-23 4:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-22 19:03 Bug? Short command line options Anatoly Borodin
2016-09-23 4:47 ` Jeff King
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).