Re: [PATCH] Documentation: update [section.subsection] to reflect what git does
- From
Jeff King <peff@peff.net>
- Date
- Oct 12, 2011, 18:34 UTC
- Message-ID
- <20111012183451.GB14543@sigill.intra.peff.net>
- In-Reply-To
- <1318434726-5556-1-git-send-email-cmn@elego.de>
On Wed, Oct 12, 2011 at 05:52:06PM +0200, Carlos Martín Nieto wrote:
Show 7 quoted lines
> -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.
OK, now having looked thoroughly at the problem again, I agree that your documentation update is much better than the one I posted earlier (technically we could still talk about canonicalizing the subsection earlier in git-config(1), but section.foo names are the deprecated minority, so it's probably not worth cluttering the page with explanations).
I do think the "compared case sensitively" bit is a little confusing here, because it's not clear what is being compared here (as we're quite deep into a discussion of the file format, and away from the git-config usage). It might be more clear to say:
With this syntax, the subsection name is converted to lower-case, and the result is compared case sensitively against the subsection name provided to git-config.
or something like that.
-Peff