From: Ayush Jha Date: Sun, 01 Mar 2026 06:13:56 GMT Subject: Re: [GSoC][PROPOSAL] Improving and Extending the git repo command Message-ID: In-Reply-To: Hi Lucas, Thank you for this feedback and for pointing out commit fac60b8925! You are completely right—assuming a blanket "relative by default" expectation ignores the historical nuance of how git rev-parse handles different path options. I have updated my proposal draft to remove that assumption and properly acknowledge the complexity of path formatting for repo-info. I also just left my thoughts on your new repo-info --path-format patch series addressing this exact issue over on that thread! Let me know if that direction seems correct. (Also, apologies if my reply to that patch series looks a bit strange in your inbox—I accidentally put Jayatheerth in the 'To' field and you in 'CC' when replying!) Thanks again for the guidance, Ayush On Sun, Mar 1, 2026 at 4:28 AM Lucas Seiki Oshiro wrote: > > > > Hi everyone, > > Hi, Ayush! > > > Note to reviewers: I'd like to hear your thoughts on whether these > > paths should default to relative or absolute. My initial thought is > > relative by default with an `--absolute` flag, as that seems to match > > user expectations for CLI tools like `git rev-parse`. > > I've just sent the path (trying to) add support for paths (the one > you mentioned). I don't know if it's the best approach. I CC'ed you > and the other GSoC applicants that are interested in git-repo-info. > > I wouldn't say that the user's expectations is to retrieve absolute > paths by default, we need to check each one of the "options for > files" modified by --path-format and see what makes more sense. > See [1]. > > [1] fac60b8925 (rev-parse: add option for absolute or relative path formatting, 2020-12-13)