threads / patch / 26924

patchDocumentation/config.txt: make truth value of numbers more explicit

Subject: [PATCH] Documentation/config.txt: make truth value of numbers more explicit

## tl;dr

One message between Mar 30, 2011 and Mar 30, 2011. Diffs are folded; open one to read it.

replies: 0people: 1as markdown or json

Carlos Martín Nieto· Mar 30, 2011, 10:22 UTC · lore

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>
---

Though if I read the source correctly, anything other than a 0 will give a true result, but it's better if we tell people to use 1.

 Documentation/config.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Show changes to Documentation/config.txt +1 −1
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 701fba9..1a571f4 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -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
 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;
 'git config' will ensure that the output is "true" or "false".
 
-- 
1.7.4.1

← back to recent threads