From 7f0a02be2f2712f66daa730e389f45e3e96f1edd Mon Sep 17 00:00:00 2001 From: Andreas Heiduk Date: Tue, 15 Aug 2017 00:12:18 +0200 Subject: doc: clarify "config --bool" behaviour with empty string `git config --bool xxx.yyy` returns `true` for `[xxx]yyy` but `false` for `[xxx]yyy=` or `[xxx]yyy=""`. This is tested in t1300-repo-config.sh since 09bc098c2. Signed-off-by: Andreas Heiduk Signed-off-by: Junio C Hamano --- Documentation/git.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'Documentation/git.txt') diff --git a/Documentation/git.txt b/Documentation/git.txt index cc215361f1..d5ddb38e56 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -571,7 +571,8 @@ example the following invocations are equivalent: Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets `foo.bar` to the boolean true value (just like `[foo]bar` would in a config file). Including the equals but with an empty value (like `git -c -foo.bar= ...`) sets `foo.bar` to the empty string. +foo.bar= ...`) sets `foo.bar` to the empty string which ` git config +--bool` will convert to `false`. --exec-path[=]:: Path to wherever your core Git programs are installed. -- cgit v1.2.3