From: Arsh Srivastava <arshsrivastava00@gmail.com>
To: git@vger.kernel.org
Subject: [Proposal][GSOC] extending git repo info with additional path metadata
Date: Sat, 4 Apr 2026 10:27:48 +0530 [thread overview]
Message-ID: <CAOAgETPYmCr=1UudOZdphjShp-kFabyVJo4sxUkXiqSBNoT5gA@mail.gmail.com> (raw)
Hi,
This is a follow up mail to proposal for [GSOC] "git repo info", it
seems that it doesn’t expose some of the path-related information that
users often end up needing, like the Git directory, working tree root,
or object directory.
In practice, users still rely on "git rev-parse" for these, which
feels a bit inconsistent given that repo info already provides a
structured way to query repository metadata.
After looking at "repo.c", it appears that the existing field-based
setup could be extended fairly easily to include these without
changing the overall design. The idea would be to add a few
path-related fields using the same getter pattern that’s already
there.
Before going further with this, it would be helpful to understand
whether this direction fits within the intended scope of "git repo
info", or if there are reasons this kind of information is
intentionally not exposed through it.
Thanks,
Arsh Srivastava
reply other threads:[~2026-04-04 4:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOAgETPYmCr=1UudOZdphjShp-kFabyVJo4sxUkXiqSBNoT5gA@mail.gmail.com' \
--to=arshsrivastava00@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).