undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: clarify "config --bool" behaviour with empty string

Browse Source 
`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@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Andreas Heiduk 2017-08-15 00:12:18 +02:00 committed by Junio C Hamano
parent 3b82744481
commit 7f0a02be2f
2 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/config.txt
View File

@ -133,15 +133,15 @@ boolean::
synonyms are accepted for 'true' and 'false'; these are all
case-insensitive.
true;; Boolean true can be spelled as `yes`, `on`, `true`,
or `1`. Also, a variable defined without `= <value>`
true;; Boolean true literals are `yes`, `on`, `true`,
and `1`. Also, a variable defined without `= <value>`
is taken as true.
false;; Boolean false can be spelled as `no`, `off`,
`false`, or `0`.
false;; Boolean false literals are `no`, `off`, `false`,
`0` and the empty string.
+
When converting value to the canonical form using `--bool` type
specifier; 'git config' will ensure that the output is "true" or
specifier, 'git config' will ensure that the output is "true" or
"false" (spelled in lowercase).
integer::

3
Documentation/git.txt
View File

@ -571,7 +571,8 @@ example the following invocations are equivalent:
Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
`foo.bar` to the boolean true value (just like `[foo]bar` would in a
config file). Including the equals but with an empty value (like `git -c
foo.bar= ...`) sets `foo.bar` to the empty string.
foo.bar= ...`) sets `foo.bar` to the empty string which ` git config
--bool` will convert to `false`.
--exec-path[=<path>]::
Path to wherever your core Git programs are installed.