diff options
| author | Carlos Martín Nieto <cmn@elego.de> | 2011-10-12 17:52:06 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2011-10-16 00:22:31 -0700 |
| commit | f737632938868adaa0e8f777235e8e15d40ab14c (patch) | |
| tree | 9a1d34eb1f865b532d9883c64f5fc63ff07c62f7 | |
| parent | 87b50542a08ac6caa083ddc376e674424e37940a (diff) | |
| download | git-cn/doc-config-bare-subsection.tar.gz | |
Documentation: update [section.subsection] to reflect what git doescn/doc-config-bare-subsection
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>
| -rw-r--r-- | Documentation/config.txt | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt index d82c0da2cf..fd998dd37c 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 |