Re: parse-options does not recognize "unspecified" behavior

On Thu, Mar 17, 2016 at 2:53 AM, Jeff King [off-list ref] wrote:

I don't think that would produce the wrong behavior, but it seems like a
very complicated solution to a problem that can easily be solved by just
following the usual conventions (that verbose starts at 0, options make
it go up or down, and "--no-" resets it to zero).

Perhaps it would make more sense if I understood what your goal was in
setting verbose to -1 in the first place.

-Peff

I am working on the micro project "configuration for commonly used
command line options like "git commit -v".
I sent out a final patch without considering the multiple verbosity
behavior of `git commit`. To take consideration for that behavior,
Junio suggested this approach [1]. I was trying to write code for this
when I noticed this behavior. I did a `git grep " unspecified " just
to find that using -1 is not that common. I think this problem can
also arise in future if some more options are included. The question
still remains whether its worth all this effort?

[1] : http://thread.gmane.org/gmane.comp.version-control.git/288820/focus=288909