From: astian <astian@eclipso.at>
To: git@vger.kernel.org
Cc: astian <astian@eclipso.at>
Subject: [PATCH 1/4] Doc/config.txt: explain repeated sections
Date: Sat, 8 Jul 2017 20:34:10 +0000 [thread overview]
Message-ID: <20170708203413.16442-2-astian@eclipso.at> (raw)
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
next prev parent reply other threads:[~2017-07-08 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 20:34 [PATCH 0/4] Misc. documentation fixes astian
2017-07-08 20:34 ` astian [this message]
2017-07-08 23:03 ` [PATCH 1/4] Doc/config.txt: explain repeated sections Junio C Hamano
2017-07-09 7:57 ` Junio C Hamano
2017-07-10 7:32 ` Jeff King
2017-07-10 16:17 ` Junio C Hamano
2017-07-08 20:34 ` [PATCH 2/4] Doc/config.txt: fix typos astian
2017-07-08 20:34 ` [PATCH 3/4] Doc/git-send-email.txt: clarify a couple of options astian
2017-07-08 20:34 ` [PATCH 4/4] Doc/config.txt: fix documentation for smtpEncryption astian
2017-07-08 23:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170708203413.16442-2-astian@eclipso.at \
--to=astian@eclipso.at \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).