Re: [GSoC PATCH v2 0/4] teach git repo info to handle path keys

From: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Date: Jun 9, 2026, 05:00 UTC
Message-ID: <CA+rGoLf39iQH9X-xKW7HeTS3sMv-N-QzGiqm0Y=RYGOAqDcaoA@mail.gmail.com>
In-Reply-To: <xmqqcxy0vevi.fsf@gitster.g>

On Tue, Jun 9, 2026 at 4:06 AM Junio C Hamano <gitster@pobox.com> wrote:

Show 13 quoted lines

>
> K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:
>
> > 2. Should we consider a default option?
> >    Currently we have path.gitdir.absolute. Should we consider an
> >    option where a plain `path.gitdir` returns some default?
>
> Probably not.  It will invite folks wanting to tweak the default
> between absolute and relative, rendering this feature useless for
> robust scripting.  You do not necessarily want to save typing in
> plumbing interface.  You want to reduce ambiguity by reducing more
> than one ways to do a thing down to just one way, and as long as
> that one way is not overly verbose, you are fine.

Makes sense. Explicit keys like path.gitdir.absolute and path.gitdir.relative are unambiguous for scripting, and saving a few keystrokes isn't worth introducing a configurable default that would make the output unpredictable. I'll actually drop question 2 from the open questions in v3's cover letter.

Thanks!

Regards,
- K Jayatheerth