Am 14.08.2017 um 19:53 schrieb Junio C Hamano:
> Andreas Heiduk <asheiduk@xxxxxxxxx> writes:
>
>> `git config --bool xxx.yyy` returns `true` for `[xxx]yyy` but
>> `false` for `[xxx]yyy=` or `[xxx]yyy=""`. This is tested in
>> t1300-repo-config.sh since 09bc098c2.
>>
>> Signed-off-by: Andreas Heiduk <asheiduk@xxxxxxxxx>
>> ---
>> Documentation/config.txt | 3 ++-
>> Documentation/git.txt | 3 ++-
>> 2 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index d5c9c4cab..d3261006b 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -221,7 +221,8 @@ boolean::
>> is taken as true.
>>
>> false;; Boolean false can be spelled as `no`, `off`,
>> - `false`, or `0`.
>> + `false`, `0`, no value (but still with `=`) or the
>> + empty string.
>
[...]
> However, I think this "no value (but still with '=')" is making it
> more confusing than necessary for two reasons.
[...]
> I notice that in this Values section (where the boolean:: is the
> first entry) there is no mention on how to spell a string value.
I assumed this is due to the pretext of the definition list:
Values of many variables are treated as a simple string, but there
are variables that take values of specific types and there are rules
as to how to spell them.
After that I would NOT expect string values to be "specific". Also: If string
values are explained here in the "Values" section, the line-breaking and escape
sequences syntax should be here too.
So my (minimal) suggestion is:
false;; Boolean false literals are `no`, `off`,
`false`, `0` and the empty string.
I'll adapt `true` in the same style and resend a patch.
