Re: [PATCH] doc: clarify "config --bool" behaviour with empty values

Andreas Heiduk writes: >> However, I think this "no value (but still with '=')" is making it >> more confusing than necessary for two reasons. > [...] > >> I notice that in this Values section (where the boolean:: is the >> first entry) there is no mention on how to spell a

Re: [PATCH] doc: clarify "config --bool" behaviour with empty values

Am 14.08.2017 um 19:53 schrieb Junio C Hamano: > Andreas Heiduk writes: > >> `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

Re: [PATCH] doc: clarify "config --bool" behaviour with empty values

Andreas Heiduk writes: > `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 > --- >

[PATCH] doc: clarify "config --bool" behaviour with empty values

`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 --- Documentation/config.txt | 3 ++- Documentation/git.txt| 3 ++- 2 files