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

[PATCH 1/4] Doc/config.txt: explain repeated sections

From
Aastian <astian@eclipso.at>
Date
Jul 8, 2017, 20:34 UTC
Message-ID
<20170708203413.16442-2-astian@eclipso.at>
In-Reply-To
<20170708203413.16442-1-astian@eclipso.at>

Add a paragraph explaining what happens when a section name is repeated in the configuration file(s).

The example configuration file shown in this document already implied Git's behaviour, this patch simply tries to make it explicit.

Signed-off-by: astian <astian@eclipso.at>
---
 Documentation/config.txt | 4 ++++
 1 file changed, 4 insertions(+)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index d5c9c4cab..afce25705 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -31,6 +31,10 @@ characters, `-` and `.` are allowed in section names.  Each variable
 must belong to some section, which means that there must be a section
 header before the first setting of a variable.
 
+Multiple occurrences of the same section are all logically merged.  (There's
+no special treatment for variables defined multiple times across physically
+different sections, the variable is simply made multivalued.)
+
 Sections can be further divided into subsections.  To begin a subsection
 put its name in double quotes, separated by space from the section name,
 in the section header, like in the example below:
-- 
2.13.2
Previous: astianNext: Junio C Hamano
Message 2 of 10 in “Misc. documentation fixes”
  1. 0/4 Misc. documentation fixesastian, Jul 8, 2017
  2. 1/4 Doc/config.txt: explain repeated sectionsastian, Jul 8, 2017
  3. Junio C HamanoJul 8, 2017
  4. Junio C HamanoJul 9, 2017
  5. Jeff KingJul 10, 2017
  6. Junio C HamanoJul 10, 2017
  7. 2/4 Doc/config.txt: fix typosastian, Jul 8, 2017
  8. 3/4 Doc/git-send-email.txt: clarify a couple of optionsastian, Jul 8, 2017
  9. 4/4 Doc/config.txt: fix documentation for smtpEncryptionastian, Jul 8, 2017
  10. Junio C HamanoJul 8, 2017

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.