From: K Jayatheerth Date: Wed, 11 Nov 2026 09:05:20 GMT Subject: Re: [GSoC Patch v8 0/7] repo: add path keys to repo info Message-ID: In-Reply-To: On Tue, Nov 10, 2026 at 1:23 AM Junio C Hamano wrote: > > K Jayatheerth 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. As echoed by Phillip below, I will avoid the hyphens. Thank you! - K Jayatheerth