Carlos Martín Nieto <cmn@xxxxxxxx> writes: > This bit me recently when I was creating a parser. See Jeff's > explanation here: > http://thread.gmane.org/gmane.comp.version-control.git/179569/focus=180290 I think you meant to focus on 180123 but anyway I think the updated text reads much better. Thanks. > Documentation/config.txt | 7 ++++--- > 1 files changed, 4 insertions(+), 3 deletions(-) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 0658ffb..1212c47 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html