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