# Bug? Short command line options

2 messages from 2016-09-22 to 2016-09-23. Participants: Anatoly Borodin, Jeff King.
Thread: https://gitlist.dev/t/44139

## Anatoly Borodin, 2016-09-22 19:03

Subject: Bug? Short command line options
Message-ID: <ns19t4$s0t$1@blaine.gmane.org>
URL: https://gitlist.dev/e/ns19t4%24s0t%241%40blaine.gmane.org

```
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


```

## Jeff King, 2016-09-23 04:47

Subject: Re: Bug? Short command line options
Message-ID: <20160923044757.7pwwzkqzkb2fqa7l@sigill.intra.peff.net>
URL: https://gitlist.dev/e/20160923044757.7pwwzkqzkb2fqa7l%40sigill.intra.peff.net
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

```