Re: [PATCH] repo: add paths.git_dir repo info key

From: Karthik Nayak <karthik.188@gmail.com>
Date: Mar 19, 2026, 14:00 UTC
Message-ID: <CAOLa=ZTx1JnxtpPiz-Cegj7eMEGZmGL8s-RJQmTWv7W4H-3UoQ@mail.gmail.com>
In-Reply-To: <pull.2242.git.git.1773766519857.gitgitgadget@gmail.com>

"Jayesh Daga via GitGitGadget" <gitgitgadget@gmail.com> writes:

Show 13 quoted lines

> From: jayesh0104 <jayeshdaga99@gmail.com>
>
> Introduce a new repo info key `paths.git_dir` to expose the
> repository's gitdir path, equivalent to `git rev-parse --git-dir`.
>
> This improves consistency and allows tools to retrieve the gitdir
> path without invoking external commands.
>
> The implementation adds support in repo.c and integrates it into
> the repo info reporting mechanism. Documentation is updated to
> describe the new key, and tests are added to verify that the value
> matches the output of `git rev-parse --git-dir`.
>

Hello Jayesh,

Seeing from the people CC'd I'm assuming that you're interested in applying for the GSoC.

As such, we encourage GSoC contributors to work on micro-projects as listed on our GSoC website and also to read the guidelines we've laid out [1] [2].

I would also mention that we do not recommend getting started on a project, unless you're selected.

Now specifically for this project, there is still no decision made about using relative paths vs absolute paths, I've highlighted this in one of the candidates proposals [3]. I would suggest getting involved in that discussion and coming to a conclusion before starting work on it.

[1]: https://git.github.io/General-Microproject-Information/ [2]: https://git.github.io/General-Application-Information/ [3]: https://lore.kernel.org/git/CAOLa=ZTtNSZ904v0-SN16jAis7gK4=MVj1g_5CGdbmaBopeZkg@mail.gmail.com/#t

Regards, Karthik

[snip]