Documentation: update [section.subsection] to reflect what git does
Using the [section.subsection] syntax, the subsection is transformed to lower-case and is matched case sensitively. Say so in the documentation and mention that you shouldn't be using it anyway. Signed-off-by: Carlos Martín Nieto <cmn@elego.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Carlos Martín Nieto committed
Oct 12, 2011 at 17:52 UTC
f737632938868adaa0e8f777235e8e15d40ab14c
1 file changed
+4
-3
Documentation/config.txt
+4
-3
@@ -45,9 +45,10 @@ lines. Variables may belong directly to a section or to a given subsection.
45
You can have `[section]` if you have `[section "subsection"]`, but you
46
don't need to.
47
48
-There is also a case insensitive alternative `[section.subsection]` syntax.
49
-In this syntax, subsection names follow the same restrictions as for section
50
-names.
48
+There is also a deprecated `[section.subsection]` syntax. With this
49
+syntax, the subsection name is converted to lower-case and is also
50
+compared case sensitively. These subsection names follow the same
51
+restrictions as section names.
52
53
All the other lines (and the remainder of the line after the section
54
header) are recognized as setting variables, in the form