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>
This commit is contained in:
Junio C Hamano 2015-03-04 11:08:34 -08:00
parent b92c1a28f8
commit 1c448b3b5c

View File

@ -54,8 +54,8 @@ restrictions as section names.
All the other lines (and the remainder of the line after the section All the other lines (and the remainder of the line after the section
header) are recognized as setting variables, in the form header) are recognized as setting variables, in the form
'name = value'. If there is no equal sign on the line, the entire line 'name = value' (or just 'name', which is a short-hand to say that
is taken as 'name' and the variable is recognized as boolean "true". the variable is the boolean "true").
The variable names are case-insensitive, allow only alphanumeric characters The variable names are case-insensitive, allow only alphanumeric characters
and `-`, and must start with an alphabetic character. and `-`, and must start with an alphabetic character.