From 1c448b3b5c283d793d994808d0ec1174b9b4dc26 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 4 Mar 2015 11:08:34 -0800 Subject: [PATCH] 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 --- Documentation/config.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index c40bf4a7ff..f1cf571fcd 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -54,8 +54,8 @@ restrictions as section names. All the other lines (and the remainder of the line after the section header) are recognized as setting variables, in the form -'name = value'. If there is no equal sign on the line, the entire line -is taken as 'name' and the variable is recognized as boolean "true". +'name = value' (or just 'name', which is a short-hand to say that +the variable is the boolean "true"). The variable names are case-insensitive, allow only alphanumeric characters and `-`, and must start with an alphabetic character. -- GitLab