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>

diff --git a/Documentation/config.txt b/Documentation/config.txt
index d82c0da2cf470dbfe7936762d4645b7509647177..fd998dd37c33bedc413209bd36053c4dec8578a3 100644 (file)
--- 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.
 
 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
 
 All the other lines (and the remainder of the line after the section
 header) are recognized as setting variables, in the form