git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC][PROPOSAL] Improving and Extending the git repo command

From
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date
Feb 28, 2026, 22:58 UTC
Message-ID
<B8697AB9-9C9B-41C9-A2D8-1848CD966137@gmail.com>
In-Reply-To
<CAFNBzOc=tuph7ecqt9TAY-aCWUkPyQ84DYjwMp3QS4-0J-wF_Q@mail.gmail.com>
> 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)
Previous: Ayush JhaNext: Ayush Jha
Message 2 of 3 in “[GSoC][PROPOSAL] Improving and Extending the git repo command”
  1. Ayush JhaFeb 28, 2026
  2. Lucas Seiki OshiroFeb 28, 2026
  3. Ayush JhaMar 1, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.