Re: [PATCH] Documentation fixes in git-config
From: Jeff King <hidden>
Date: 2016-06-15 22:50:26
On Wed, Jan 19, 2011 at 03:14:01PM +0100, Libor Pechacek wrote:
quoted hunk ↗ jump to hunk
diff --git a/Documentation/config.txt b/Documentation/config.txt index ff7c225..0f23bc7 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt@@ -12,8 +12,9 @@ The configuration variables are used by both the git plumbing and the porcelains. The variables are divided into sections, wherein the fully qualified variable name of the variable itself is the last dot-separated segment and the section name is everything before the last -dot. The variable names are case-insensitive and only alphanumeric -characters are allowed. Some variables may appear multiple times. +dot. The variable names are case-insensitive, only alphanumeric +characters and '-' are allowed and must start with an alphabetic character. +Some variables may appear multiple times.
The intent of the change looks fine, but your sentence doesn't quite parse to me (to be fair, the problem is in the one you are replacing, but adding the third clause makes it even more confusing). How about: The variables names are case-insensitive, allow only alphanumeric characters and '-', and must start with an alphabetic character.
--get-regexp:: Like --get-all, but interprets the name as a regular expression. - Also outputs the key names. + Regular expression matching is case sensitive in all parts of the key, + therefore make sure your pattern matches lower case letters in section + and variable names. Also outputs the key names.
That is only true because of the breakage in your first patch. Without your patch, both of these work: git config --get-regexp 'Foo.*' git config --get-regexp 'foo.*' That being said, the downcasing is extremely naive for regexps, and you should try to match the canonical name. The current downcasing behavior should probably stay for historical reasons, but is not well thought-out (it may even be accidental). Perhaps we should therefore explain it in those terms: Regular expression matching is case-sensitive and done against a canonicalized version of the key in which section and variable names are lowercased, but subsection names are not. For historical reasons, some simple regular expressions are lower-cased before matching (everything before the first dot and after the last dot), which makes things like "Core.*' work. I dunno. Maybe we should just declare "Core.*' to be broken, and anybody who was relying on it is wrong. -Peff