Re: [GSoC Patch v8 0/7] repo: add path keys to repo info

[Junio C Hamano <gitster@pobox.com>]

K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:

>> >    - `path.superproject-root.absolute` / `path.superproject-root.relative`:
>> >      The root of the superproject when inside a submodule.
>>
>> Personally, I'd prefer "path.superproject-working-tree.*" here, though I
>> see Justin thought that was a bit of a mouthful. As this command is for
>> use in scripts I'd rather have a descriptive name.
>
> I don't have an opinion on the name itself, but, that said:
> I think superproject-working-tree is a more suiting name.

Syntactically you could put anything at the second level of
three-level configuration variable names, but I thought we avoid '-'
in configuration variable names in general.

We can see that we made many mistakes in the 'maintenance.'
hierarchy ...

$ git grep -h -E '^`?[^ ]*::$' Documentation/config/ | grep -e -

... but nowhere else.