On Mon, Dec 17, 2007 at 07:28:47AM +0000, Junio C Hamano wrote: > This comes directly on top of gitcli documentation patch and is intended > to be squashed into it. I obviously ack. > -Another things to keep in mind is that long options can be negated. For > +Boolean options with long option names can be negated by prefixing `"--no-"`. For ^^^^^^^ Though this isn't correct: you can negate any kind of option, even one with strings arguments, and it does makes sense. E.g. if you have some: foo.stringOpt = "value" in your gitconfig file, then it's very handy to be able to write: $ git foo --no-string-opt to be sure the gitconfig from the user won't mess with what you intend to do. The negation of commands can be disabled (in the recent iterations of parseopt) using a flag I don't recall the name, but it's on by default even for non boolean options. It may make sense to do a re-read pass of all options and see which ones it makes sense to negate and which not. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpLEaYsBTKZ1.pgp
Description: PGP signature
