Skip to content

Commit a5285b6

Browse files
committed
Documentation/config.txt: explain multi-valued variables once
The syntax section repeats what the preamble explained already. That a variable can have multiple values is more about what a variable is than the syntax of the file. Signed-off-by: Junio C Hamano <[email protected]>
1 parent 05c3e5c commit a5285b6

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

Documentation/config.txt

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,8 @@ the fully qualified variable name of the variable itself is the last
1414
dot-separated segment and the section name is everything before the last
1515
dot. The variable names are case-insensitive, allow only alphanumeric
1616
characters and `-`, and must start with an alphabetic character. Some
17-
variables may appear multiple times.
17+
variables may appear multiple times; we say then that the variable is
18+
multivalued.
1819

1920
Syntax
2021
~~~~~~
@@ -56,9 +57,7 @@ header) are recognized as setting variables, in the form
5657
'name = value'. If there is no equal sign on the line, the entire line
5758
is taken as 'name' and the variable is recognized as boolean "true".
5859
The variable names are case-insensitive, allow only alphanumeric characters
59-
and `-`, and must start with an alphabetic character. There can be more
60-
than one value for a given variable; we say then that the variable is
61-
multivalued.
60+
and `-`, and must start with an alphabetic character.
6261

6362
Leading and trailing whitespace in a variable value is discarded.
6463
Internal whitespace within a variable value is retained verbatim.

0 commit comments

Comments
 (0)