Re: [PATCH] builtin-push: New long option --verbose

Why?

Junio C Hamano [off-list ref] writes:

Why?

One reason is that I often don't know if the program I want to run
(git or something sles) uses -v as the "verbose" flag, or if it's the
"version" flag or something else.  But if there is a --verbose flag, I
can be sure what it is, so I often try that first if I'm unsure.  If
that faild, I'll probably look in the man page.

-- 
David Kågedal

Junio C Hamano [off-list ref] writes:

Why?

It complements the command set. -v was the only lonely that did not
have long option choice.

Overall, the option handling in every command could use aboot to
provide both short and long options. Now various commands have short
ones, but no long ones, or vice versa. It's like sherwood there.

Let's start unifying.
Jari

Hi,

On Mon, 27 Aug 2007, Jari Aalto wrote:

Junio C Hamano [off-list ref] writes:

quoted

Why?

It complements the command set. -v was the only lonely that did not
have long option choice.

Of course, the _proper_ solution would be to introduce a complete option 
parser component a la getopt.  For me, it is not _half_ as annoying that 
some short/long options are missing than being unable to abbreviate the 
short options into something like "-nls".

Ciao,
Dscho