Re: [GSoC Patch v8 0/7] repo: add path keys to repo info
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 9, 2026, 19:53 UTC
- Message-ID
- <xmqq5wy5zsqy.fsf@gitster.g>
- In-Reply-To
- <CA+rGoLef6b35hjJAcO5Nm57NiyDGK-iDbWO2MUMeoKVCkbRf5A@mail.gmail.com>
K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:
Show 9 quoted lines
>> > - `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.