Skip to content

Commit 1c448b3

Browse files
committed
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 <[email protected]>
1 parent b92c1a2 commit 1c448b3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/config.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ restrictions as section names.
5454

5555
All the other lines (and the remainder of the line after the section
5656
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").
5959
The variable names are case-insensitive, allow only alphanumeric characters
6060
and `-`, and must start with an alphabetic character.
6161

0 commit comments

Comments
 (0)