git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 17:26 UTC

Re: [PATCH 0/4] repo: add support for path-related fields

From
JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com>
Date
Mar 3, 2026, 02:48 UTC
Message-ID
<CA+rGoLfbzXqP1Tw+94jMmWcSGPoefMv5E_fvwriad-O5CUeKHQ@mail.gmail.com>
In-Reply-To
<3983da40-bf2c-4665-a7d9-dfebaacb8bd3@gmail.com>
Show 6 quoted lines
>
> Short question: Is using format modifier like (%path:relative),
> (%path:absolute) a good solution here? I think it can be implemented by
> simply adding a path parsing function in ref-filter.c (and some other
> work that aren't particularly challenging).
>

I see your point here. but wouldn't this effectively be the same as Ayush's suggestion, just with a different syntax? Whether we use distinct keys (path.absolute.toplevel) or format modifiers (%(path:absolute)) It would still result in almost the same internals.

Show 7 quoted lines
>
> Short question: Is using format modifier like (%path:relative),
> (%path:absolute) a good solution here? I think it can be implemented by
> simply adding a path parsing function in ref-filter.c (and some other
> work that aren't particularly challenging).
>
> It should be user-friendly, readable and free of global flags, right? :-]
I don't think the syntax is a concern, even if both of them are equally verbose.

Coming to user friendliness I believe Junio has already raised an appropriate question.

Previous: Junio C HamanoNext: Ayush Jha
Message 20 of 26 in “repo: add support for path-related fields”
  1. 0/4 repo: add support for path-related fieldsLucas Seiki Oshiro, Feb 28, 2026
  2. 1/4 rev-parse: prepend `path_` to path-related enumsLucas Seiki Oshiro, Feb 28, 2026
  3. 2/4 path: add new function strbuf_add_pathLucas Seiki Oshiro, Feb 28, 2026
  4. 3/4 repo: add the --format-path flagLucas Seiki Oshiro, Feb 28, 2026
  5. 4/4 repo: add the field path.toplevelLucas Seiki Oshiro, Feb 28, 2026
  6. JAYATHEERTH KMar 1, 2026
  7. Tian YuchenMar 1, 2026
  8. Ayush JhaMar 1, 2026
  9. JAYATHEERTH KMar 1, 2026
  10. Phillip WoodMar 1, 2026
  11. Lucas Seiki OshiroMar 1, 2026
  12. Lucas Seiki OshiroMar 1, 2026
  13. Lucas Seiki OshiroMar 1, 2026
  14. Lucas Seiki OshiroMar 1, 2026
  15. brian m. carlsonMar 1, 2026
  16. Tian YuchenMar 2, 2026
  17. Junio C HamanoMar 2, 2026
  18. Tian YuchenMar 2, 2026
  19. Junio C HamanoMar 2, 2026
  20. JAYATHEERTH KMar 3, 2026
  21. Ayush JhaMar 3, 2026
  22. Tian YuchenMar 3, 2026
  23. JAYATHEERTH KMar 3, 2026
  24. Tian YuchenMar 3, 2026
  25. JAYATHEERTH KMar 3, 2026
  26. Lucas Seiki OshiroMar 8, 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.