Re: [PATCH 2/3] parse_config_key: allow matching single-level config

On Fri, Feb 24, 2017 at 01:20:48PM -0800, Junio C Hamano wrote: > Jeff King writes: > > > The parse_config_key() function was introduced to make it > > easier to match "section.subsection.key" variables. It also > > handles the simpler "section.key", and the caller is > >

Re: [PATCH 2/3] parse_config_key: allow matching single-level config

Jeff King writes: > The parse_config_key() function was introduced to make it > easier to match "section.subsection.key" variables. It also > handles the simpler "section.key", and the caller is > responsible for distinguishing the two from its > out-parameters. > > Most callers

Re: [PATCH 2/3] parse_config_key: allow matching single-level config

Junio C Hamano writes: > Jeff King writes: > >> The parse_config_key() function was introduced to make it >> easier to match "section.subsection.key" variables. It also >> handles the simpler "section.key", and the caller is >> responsible for distinguishing

[PATCH 2/3] parse_config_key: allow matching single-level config

The parse_config_key() function was introduced to make it easier to match "section.subsection.key" variables. It also handles the simpler "section.key", and the caller is responsible for distinguishing the two from its out-parameters. Most callers who _only_ want "section.key" would just use a