{"thread":{"id":"65430","subject":"[Proposal][GSOC] extending git repo info with additional path metadata","startedAt":"2026-04-04T04:58:00Z","lastAt":"2026-04-04T04:58:00Z","messageCount":1,"participants":["Arsh Srivastava"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"540868","messageId":"CAOAgETPYmCr=1UudOZdphjShp-kFabyVJo4sxUkXiqSBNoT5gA@mail.gmail.com","threadId":"65430","inReplyTo":null,"subject":"[Proposal][GSOC] extending git repo info with additional path metadata","fromName":"Arsh Srivastava","fromEmail":"arshsrivastava00@gmail.com","sentAt":"2026-04-04T04:57:48Z","receivedAt":"2026-04-04T04:58:00Z","isPatch":false,"body":"Hi,\n\nThis is a follow up mail to proposal for [GSOC] \"git repo info\", it\nseems that it doesn’t expose some of the path-related information that\nusers often end up needing, like the Git directory, working tree root,\nor object directory.\n\nIn practice, users still rely on \"git rev-parse\" for these, which\nfeels a bit inconsistent given that repo info already provides a\nstructured way to query repository metadata.\n\nAfter looking at \"repo.c\", it appears that the existing field-based\nsetup could be extended fairly easily to include these without\nchanging the overall design. The idea would be to add a few\npath-related fields using the same getter pattern that’s already\nthere.\n\nBefore going further with this, it would be helpful to understand\nwhether this direction fits within the intended scope of \"git repo\ninfo\", or if there are reasons this kind of information is\nintentionally not exposed through it.\n\nThanks,\nArsh Srivastava\n"}]}