Documentation/config.txt: make truth value of numbers more explicit
Change the order to 1/0 to have the same true/false order as the rest of the possibilities for a boolean variable in order not not confuse users. Signed-off-by: Carlos Martín Nieto <cmn@elego.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
2f8ee02c49
commit
18b19e443b
@ -62,7 +62,7 @@ Internal whitespace within a variable value is retained verbatim.
|
|||||||
|
|
||||||
The values following the equals sign in variable assign are all either
|
The values following the equals sign in variable assign are all either
|
||||||
a string, an integer, or a boolean. Boolean values may be given as yes/no,
|
a string, an integer, or a boolean. Boolean values may be given as yes/no,
|
||||||
0/1, true/false or on/off. Case is not significant in boolean values, when
|
1/0, true/false or on/off. Case is not significant in boolean values, when
|
||||||
converting value to the canonical form using '--bool' type specifier;
|
converting value to the canonical form using '--bool' type specifier;
|
||||||
'git config' will ensure that the output is "true" or "false".
|
'git config' will ensure that the output is "true" or "false".
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user