Jeff King writes:
> FWIW, the use of "multivalued" here tickled my spider sense, too. I
> think when talking on the list we generally reserve "multivalued" for
> true "we expect this to be a list" variables. But the only mention of
> "multivalued" in the config documentation seems
On Sun, Jul 09, 2017 at 12:57:07AM -0700, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> >> +Multiple occurrences of the same section are all logically merged.
> >> (There's
> >> +no special treatment for variables defined multiple times across
> >> physically
> >>
Junio C Hamano writes:
>> +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.)
>> +
>
> Looks correct;
astian writes:
> 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:
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
---
5 matches
Mail list logo