summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2011-10-21 16:04:33 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-10-21 16:04:33 -0700
commitabe277301996d4b30f2c8f48cf92dcf677af783d (patch)
tree49e8332528f8fca9a6ae929c3e8afdff0bd8e53a /Documentation
parentMerge branch 'jk/maint-pack-objects-compete-with-delete' (diff)
parentDocumentation: update [section.subsection] to reflect what git does (diff)
downloadtgif-abe277301996d4b30f2c8f48cf92dcf677af783d.tar.xz
Merge branch 'cn/doc-config-bare-subsection'
* cn/doc-config-bare-subsection: Documentation: update [section.subsection] to reflect what git does
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/config.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt
index b30c7e6278..9c81fffc61 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -45,9 +45,10 @@ lines. Variables may belong directly to a section or to a given subsection.
You can have `[section]` if you have `[section "subsection"]`, but you
don't need to.
-There is also a case insensitive alternative `[section.subsection]` syntax.
-In this syntax, subsection names follow the same restrictions as for section
-names.
+There is also a deprecated `[section.subsection]` syntax. With this
+syntax, the subsection name is converted to lower-case and is also
+compared case sensitively. These subsection names follow the same
+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