From: Carlos Martín Nieto Date: Wed, 12 Oct 2011 15:52:06 +0000 (+0200) Subject: Documentation: update [section.subsection] to reflect what git does X-Git-Tag: v1.7.8-rc0~26^2 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=f737632938868adaa0e8f777235e8e15d40ab14c;p=git.git 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 Signed-off-by: Junio C Hamano --- diff --git a/Documentation/config.txt b/Documentation/config.txt index d82c0da2c..fd998dd37 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