git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: should config options be treated as case-sensitive?

From
Junio C Hamano <gitster@pobox.com>
Date
May 23, 2018, 23:33 UTC
Message-ID
<xmqq8t8aueu7.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<alpine.LFD.2.21.1805230503500.18721@localhost.localdomain>
"Robert P. J. Day" <rpjday@crashcourse.ca> writes:
Show 5 quoted lines
>> Unfortunately, that line of thinking leads us to madness, as you are
>> exhibiting the typical symptom of "my today's immediate itch is the
>> most important one in the world"-itis....
>
>   fair enough, point taken.
FWIW, everybody suffers from it, including me.

I was trying to come up with an update, and here is an attempted rewrite of the earlier section. I am not sure if this is a good direction to go in, but if so, we'd need to reduce the duplicated info from the Syntax section that immediately follows.

 Documentation/config.txt | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)
diff --git i/Documentation/config.txt w/Documentation/config.txt
index 84e2891aed..5b79411b4b 100644
--- i/Documentation/config.txt
+++ w/Documentation/config.txt
@@ -9,13 +9,21 @@ fallback values for the `.git/config` file. The file `/etc/gitconfig`
 can be used to store a system-wide default configuration.
 
 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, allow only alphanumeric
-characters and `-`, and must start with an alphabetic character.  Some
-variables may appear multiple times; we say then that the variable is
-multivalued.
+and the porcelains. The variables are divided into sections, and some
+sections can have subsections.  In a variable name that is fully
+spelled out, the part up to the first dot is the section, the part
+after the last dot is the variable.  If these two dots are not the
+same, what's in the middle is the subsection.
+
+The section and the variable names are case-insensitive, allow only
+alphanumeric characters and `-`, and must start with an alphabetic
+character.  Often multi-word variable names are spelled in CamelCase
+by convention for extra readability.
+
+Some variables may appear multiple times and their effects accumulate;
+we say then that such a variable is multivalued.  For other variables, 
+when they appear more than once, the last one takes effect.
+
 
 Syntax
 ~~~~~~
Previous: Robert P. J. Day
Message 8 of 8 in “should config options be treated as case-sensitive?”
  1. Robert P. J. DayMay 22, 2018
  2. Ævar Arnfjörð BjarmasonMay 22, 2018
  3. Robert P. J. DayMay 22, 2018
  4. Junio C HamanoMay 23, 2018
  5. Robert P. J. DayMay 23, 2018
  6. Junio C HamanoMay 23, 2018
  7. Robert P. J. DayMay 23, 2018
  8. Junio C HamanoMay 23, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.