Documentation/config.txt: simplify boolean description in the syntax section
The 'true' short-hand doesn't deserve a separate sentence; even our own git config --bool foo.bar yes would not produce it. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 4, 2015 at 11:08 UTC
1c448b3b5c283d793d994808d0ec1174b9b4dc26
1 file changed
+2
-2
Documentation/config.txt
+2
-2
@@ -54,8 +54,8 @@ restrictions as section names.
54
55
All the other lines (and the remainder of the line after the section
56
header) are recognized as setting variables, in the form
57
-'name = value'. If there is no equal sign on the line, the entire line
58
-is taken as 'name' and the variable is recognized as boolean "true".
57
+'name = value' (or just 'name', which is a short-hand to say that
58
+the variable is the boolean "true").
59
The variable names are case-insensitive, allow only alphanumeric characters
60
and `-`, and must start with an alphabetic character.
61