Re: [PATCH 3/6] Refactor --dirstat parsing; deprecate --cumulative and --dirstat-by-file
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 27, 2011, 04:53 UTC
- Message-ID
- <7vaafcb8ho.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <201104270402.10658.johan@herland.net>
Johan Herland <johan@herland.net> writes:
> I have tried to consistently use "option" for referring to the entire > "--dirstat=whatever" entity, and then use "argument" for referring to > each comma-separated token following "--dirstat=".
Ok.
Your terminology is pretty much consistent with how POSIX calls these things (Cf. *1*, *2*)
* -X is an OPTION; * 3 in -X3 is an OPTION ARGUMENT; and * OPTION ARGUMENT is explained as "A parameter that follows certain options".
Between "--option=parameter" or "--option=option argument", the former is easier to type and read, so it is slightly more preferable.
Show 9 quoted lines
>> > +-- >> > +`changes`;; >> > + Compute the dirstat numbers by counting the lines that have been >> > + removed from the source, or added to the destination. This ignores >> > + the amount of pure code movements within a file. In other words, >> > + rearranging lines in a file is not counted as much as other changes. >> > + This is the default `--dirstat` behavior. >> >> "default behavior when no parameter is given"?
Right. Thanks.
[References]
*1* 12.1 Utility Argument Syntax
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html#tag_12_01
*2* 3.256 Option, 3.257 Option-Argument
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_256.