aboutsummaryrefslogtreecommitdiff
path: root/Documentation/git.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-09-19 14:05:10 -0700
committerJunio C Hamano <gitster@pobox.com>2014-09-19 14:05:10 -0700
commit04cd47f553796263451c946061e175d847f388c3 (patch)
tree24bad2f1f907961c2e2af06f395b8b0fb3258fc7 /Documentation/git.txt
parent723361a572e8c9fe93f00b17a1f4ed02585923b2 (diff)
parenta789ca70e7a5b02973b116d21674acd795238f99 (diff)
downloadgit-04cd47f553796263451c946061e175d847f388c3.tar.gz
git-04cd47f553796263451c946061e175d847f388c3.tar.xz
Merge branch 'jk/command-line-config-empty-string' into maint
* jk/command-line-config-empty-string: config: teach "git -c" to recognize an empty string Conflicts: config.c
Diffstat (limited to 'Documentation/git.txt')
-rw-r--r--Documentation/git.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/git.txt b/Documentation/git.txt
index de7b870a3..26de4dd54 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -452,6 +452,11 @@ example the following invocations are equivalent:
given will override values from configuration files.
The <name> is expected in the same format as listed by
'git config' (subkeys separated by dots).
++
+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.
--exec-path[=<path>]::
Path to wherever your core Git programs are installed.