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

Re: [GSoC Patch v5 2/4] rev-parse: use append_formatted_path() for path formatting

From
K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Date
Jun 16, 2026, 17:04 UTC
Message-ID
<CA+rGoLfhhRNrSReeJ1grhy+2K3BSrikTCNgGpCaGqc4fFp3Lfg@mail.gmail.com>
In-Reply-To
<0077b1ae-3c85-4b34-a0ac-766395157c4f@gmail.com>

Hi Phillip, Thanks for taking a look!

Show 15 quoted lines
> On 16/06/2026 05:49, K Jayatheerth wrote:
> > The path-formatting logic in builtin/rev-parse.c is tightly coupled
> > to that command and writes directly to stdout, making it impossible
> > for other builtins to reuse.
> >
> > Extract the core algorithm into append_formatted_path() in path.c
> > and expose a path_format enum in path.h so that any builtin can
> > format paths consistently without duplicating logic.
>
> Sorry I haven't had time to look at this series recently, it is looking
> much nicer now that we have a single enum. It would be helpful to
> explain why we need PATH_FORMAT_DEFAULT that acts exactly like
> PATH_FORMAT_UNMODIFIED. Looking at the next patch it seems this is still
> a wart in the api due to rev-parse wanting needing to distinguish the
> unmodified case from the default case.
t);
Show 5 quoted lines
> > +
> >   # ifdef USE_THE_REPOSITORY_VARIABLE
> >   #  include "strbuf.h"
> >   #  include "repository.h"
>
Show 14 quoted lines
> >   int cmd_rev_parse(int argc,
> > @@ -717,7 +661,7 @@ int cmd_rev_parse(int argc,
> >       const char *name = NULL;
> >       struct strbuf buf = STRBUF_INIT;
> >       int seen_end_of_options = 0;
> > -     enum format_type format = FORMAT_DEFAULT;
> > +     enum path_format arg_path_format = PATH_FORMAT_DEFAULT;
>
> This is the source of the api wart I referred to in the previous patch.
> Could we keep the existing enums and convert them into the appropriate
> PATH_FORMAT_* flag in print_path() above? I think we already have the
> logic to do that in the existing code. That would mean that other users
> of append_formatted_path() don't have to worry about the extra flag.
>
That is a much more elegant solution than the current one.

For v6, I will clean this up by keeping the fallback logic localized within builtin/rev-parse.c and removing PATH_FORMAT_DEFAULT entirely from enum path_format in path.h.

Instead, I'll re-introduce a small local enum (e.g., enum rev_parse_format) inside rev-parse.c to handle the command-line parsing state (tracking whether the user explicitly provided a flag or if we are still in a neutral/default state).

As you said, most of the logic is already present. In print_path(), we will check that local tracking enum. If it’s set to the local default, we can map it directly to the path-specific def_format before invoking append_formatted_path(). This ensures other users of the function don't have to worry about the extra flag.

I will send out the v6 series with these fixes shortly.
Regards,
- K Jayatheerth
Previous: Phillip WoodNext: Phillip Wood
Message 58 of 82 in “teach git repo info to handle path keys”
  1. K JayatheerthJun 1, 2026
  2. [GSoC][PATCH 1/4] path: add strbuf_add_path for formatting pathsK Jayatheerth, Jun 1, 2026
  3. Phillip WoodJun 2, 2026
  4. [GSoC][PATCH 2/4] rev-parse: use strbuf_add_path for path formattingK Jayatheerth, Jun 1, 2026
  5. [GSoC][PATCH 3/4] repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 1, 2026
  6. Lucas Seiki OshiroJun 1, 2026
  7. Junio C HamanoJun 1, 2026
  8. [GSoC][PATCH 4/4] repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 1, 2026
  9. Lucas Seiki OshiroJun 1, 2026
  10. Lucas Seiki OshiroJun 1, 2026
  11. Lucas Seiki OshiroJun 1, 2026
  12. Lucas Seiki OshiroJun 1, 2026
  13. Junio C HamanoJun 1, 2026
  14. Phillip WoodJun 2, 2026
  15. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 5, 2026
  16. 1/4 path: introduce format_path() for centralized path formattingK Jayatheerth, Jun 5, 2026
  17. Kristoffer HaugsbakkJun 5, 2026
  18. K JayatheerthJun 9, 2026
  19. Lucas Seiki OshiroJun 8, 2026
  20. K JayatheerthJun 9, 2026
  21. Justin ToblerJun 8, 2026
  22. 2/4 rev-parse: use format_path for path formattingK Jayatheerth, Jun 5, 2026
  23. Justin ToblerJun 8, 2026
  24. 3/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 5, 2026
  25. Justin ToblerJun 8, 2026
  26. K JayatheerthJun 9, 2026
  27. Justin ToblerJun 9, 2026
  28. K JayatheerthJun 10, 2026
  29. Lucas Seiki OshiroJun 8, 2026
  30. 4/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 5, 2026
  31. Lucas Seiki OshiroJun 8, 2026
  32. Lucas Seiki OshiroJun 5, 2026
  33. K JayatheerthJun 9, 2026
  34. Junio C HamanoJun 8, 2026
  35. K JayatheerthJun 9, 2026
  36. Lucas Seiki OshiroJun 10, 2026
  37. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 12, 2026
  38. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 12, 2026
  39. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 12, 2026
  40. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 12, 2026
  41. Lucas Seiki OshiroJun 15, 2026
  42. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 12, 2026
  43. Lucas Seiki OshiroJun 15, 2026
  44. Lucas Seiki OshiroJun 15, 2026
  45. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 15, 2026
  46. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 15, 2026
  47. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 15, 2026
  48. Justin ToblerJun 15, 2026
  49. K JayatheerthJun 16, 2026
  50. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 15, 2026
  51. Justin ToblerJun 15, 2026
  52. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 15, 2026
  53. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 16, 2026
  54. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 16, 2026
  55. Phillip WoodJun 16, 2026
  56. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 16, 2026
  57. Phillip WoodJun 16, 2026
  58. K JayatheerthJun 16, 2026
  59. Phillip WoodJun 16, 2026
  60. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 16, 2026
  61. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 16, 2026
  62. 0/4 teach git repo info to handle path keysK Jayatheerth, Jun 20, 2026
  63. 1/4 path: introduce append_formatted_path() for shared path formattingK Jayatheerth, Jun 20, 2026
  64. Junio C HamanoJun 20, 2026
  65. K JayatheerthJun 20, 2026
  66. 2/4 rev-parse: use append_formatted_path() for path formattingK Jayatheerth, Jun 20, 2026
  67. 3/4 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 20, 2026
  68. 4/4 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 20, 2026
  69. 0/3 teach git repo info to handle path keysK Jayatheerth, Jun 21, 2026
  70. 1/3 path: extract append_formatted_path() and use in rev-parseK Jayatheerth, Jun 21, 2026
  71. Junio C HamanoJun 21, 2026
  72. Junio C HamanoJun 22, 2026
  73. K JayatheerthJun 22, 2026
  74. Phillip WoodJun 23, 2026
  75. K JayatheerthJun 24, 2026
  76. 2/3 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 21, 2026
  77. 3/3 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 21, 2026
  78. 0/3 teach git repo info to handle path keysK Jayatheerth, Jun 24, 2026
  79. 1/3 path: extract format_path() and use in rev-parseK Jayatheerth, Jun 24, 2026
  80. Junio C HamanoJun 24, 2026
  81. 2/3 repo: add path.commondir with absolute and relative suffix formattingK Jayatheerth, Jun 24, 2026
  82. 3/3 repo: add path.gitdir with absolute and relative suffix formattingK Jayatheerth, Jun 24, 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.