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

Re: [PATCH 1/3] repo: extend info paths and structure statistics

From
Justin Tobler <jltobler@gmail.com>
Date
Feb 23, 2026, 03:02 UTC
Message-ID
<aZvBLAvM0rfA8VUr@denethor>
In-Reply-To
<9f2b3a46a4475ef9dcfec65def3a9965b476b4c4.1771784936.git.gitgitgadget@gmail.com>
On 26/02/22 06:28PM, eslam-reda-div via GitGitGadget wrote:
Show 16 quoted lines
> From: eslam-reda-div <eslam.reda.div@gmail.com>
> 
> Improve git repo info by adding path-oriented keys that match values
> users currently obtain from git rev-parse, including common directory,
> git directory, top-level, superproject working tree, and additional
> git-path based locations.
> 
> Teach git repo info to accept category keys like layout and path,
> and add --path-format=(absolute|relative) so scripts can request the
> desired path style explicitly. The command now uses repository context
> passed to the command path instead of relying on global state.
> 
> Extend git repo structure with deeper repository metrics inspired by
> git-sizer, including per-type maximum inflated and on-disk object sizes,
> maximum commit parent count, maximum tree entry count, longest/deepest
> blob path, and deepest annotated tag chain.
Hello,

Just FYI, there is already a series on the list I'm currently working on that is extending the "structure" output for git-repo [1] similar to what is being done here. This series collects largest inflated object info, max commit parents, and max tree entries. It does look like this series is collecting a couple of other data points too, but maybe we could do so it a separate followup series to the one I'm working on? :)

Thanks, -Justin

[1]: https://lore.kernel.org/git/20260203221758.1164434-1-jltobler@gmail.com/
Previous: Lucas Seiki OshiroNext: Eslam reda ragheb via GitGitGadget
Message 4 of 68 in “repo: extend info path reporting and structure statistics”
  1. 0/3 repo: extend info path reporting and structure statisticseslam reda via GitGitGadget, Feb 22, 2026
  2. 1/3 repo: extend info paths and structure statisticseslam-reda-div via GitGitGadget, Feb 22, 2026
  3. Lucas Seiki OshiroFeb 22, 2026
  4. Justin ToblerFeb 23, 2026
  5. 2/3 t1900,t1901: make repo tests hash-agnostic and wc-portableEslam reda ragheb via GitGitGadget, Feb 22, 2026
  6. Lucas Seiki OshiroFeb 22, 2026
  7. 3/3 t1900,t1901: fix test portability issuesEslam reda ragheb via GitGitGadget, Feb 22, 2026
  8. Junio C HamanoFeb 22, 2026
  9. 0/9 repo: extend info path reporting and structure statisticseslam reda via GitGitGadget, Feb 23, 2026
  10. 1/9 repo: teach info context and category keysEslam reda ragheb via GitGitGadget, Feb 23, 2026
  11. 2/9 repo: add path keys to repo infoEslam reda ragheb via GitGitGadget, Feb 23, 2026
  12. 4/9 repo: add structure max object size metricsEslam reda ragheb via GitGitGadget, Feb 23, 2026
  13. 5/9 repo: add structure topology and path-depth metricsEslam reda ragheb via GitGitGadget, Feb 23, 2026
  14. 6/9 repo: add aggregate structure totals to keyvalue outputEslam reda ragheb via GitGitGadget, Feb 23, 2026
  15. 7/9 t1900: cover repo info path keys and path-formatEslam reda ragheb via GitGitGadget, Feb 23, 2026
  16. 8/9 t1901: extend structure metric coverage and portabilityEslam reda ragheb via GitGitGadget, Feb 23, 2026
  17. 9/9 docs: describe repo info path keys and structure metricsEslam reda ragheb via GitGitGadget, Feb 23, 2026
  18. 0/5 repo: extend info path reporting and structure statisticseslam reda via GitGitGadget, Feb 23, 2026
  19. 1/5 repo: teach info context and category keysEslam reda ragheb via GitGitGadget, Feb 23, 2026
  20. 2/5 repo: add path keys to repo infoEslam reda ragheb via GitGitGadget, Feb 23, 2026
  21. 3/5 repo: add --path-format for info path outputEslam reda ragheb via GitGitGadget, Feb 23, 2026
  22. 4/5 t1900: cover repo info path keys and path-formatEslam reda ragheb via GitGitGadget, Feb 23, 2026
  23. 5/5 docs: describe repo info path keysEslam reda ragheb via GitGitGadget, Feb 23, 2026
  24. 00/10 repo info: add category/path keys and --path-formateslam reda via GitGitGadget, Feb 26, 2026
  25. 01/10 repo: teach info context and category keysEslam reda ragheb via GitGitGadget, Feb 26, 2026
  26. Junio C HamanoFeb 26, 2026
  27. 02/10 repo: add path keys to repo infoEslam reda ragheb via GitGitGadget, Feb 26, 2026
  28. Junio C HamanoFeb 26, 2026
  29. Phillip WoodFeb 27, 2026
  30. Junio C HamanoFeb 27, 2026
  31. Phillip WoodMar 1, 2026
  32. Junio C HamanoMar 2, 2026
  33. 03/10 repo: add --path-format for info path outputEslam reda ragheb via GitGitGadget, Feb 26, 2026
  34. 04/10 repo: add structure max object size metricsEslam reda ragheb via GitGitGadget, Feb 26, 2026
  35. 05/10 repo: add structure topology and path-depth metricsEslam reda ragheb via GitGitGadget, Feb 26, 2026
  36. 06/10 repo: add aggregate structure totals to keyvalue outputEslam reda ragheb via GitGitGadget, Feb 26, 2026
  37. 07/10 t1900: cover repo info path keys and path-formatEslam reda ragheb via GitGitGadget, Feb 26, 2026
  38. 08/10 t1901: extend structure metric coverage and portabilityEslam reda ragheb via GitGitGadget, Feb 26, 2026
  39. 09/10 docs: describe repo info path keys and structure metricsEslam reda ragheb via GitGitGadget, Feb 26, 2026
  40. 10/10 repo: reduce repetition in structure keyvalue outputEslam reda ragheb via GitGitGadget, Feb 26, 2026
  41. 00/11 repo info: add category/path keys and --path-formateslam reda via GitGitGadget, Feb 27, 2026
  42. 01/11 repo: teach info context and category keysEslam reda ragheb via GitGitGadget, Feb 27, 2026
  43. Lucas Seiki OshiroFeb 27, 2026
  44. 02/11 repo: add path keys to repo infoEslam reda ragheb via GitGitGadget, Feb 27, 2026
  45. 03/11 repo: add --path-format for info path outputEslam reda ragheb via GitGitGadget, Feb 27, 2026
  46. 04/11 repo: add structure max object size metricsEslam reda ragheb via GitGitGadget, Feb 27, 2026
  47. 05/11 repo: add structure topology and path-depth metricsEslam reda ragheb via GitGitGadget, Feb 27, 2026
  48. 06/11 repo: add aggregate structure totals to keyvalue outputEslam reda ragheb via GitGitGadget, Feb 27, 2026
  49. 07/11 t1900: cover repo info path keys and path-formatEslam reda ragheb via GitGitGadget, Feb 27, 2026
  50. 08/11 t1901: extend structure metric coverage and portabilityEslam reda ragheb via GitGitGadget, Feb 27, 2026
  51. 09/11 docs: describe repo info path keys and structure metricsEslam reda ragheb via GitGitGadget, Feb 27, 2026
  52. 10/11 repo: reduce repetition in structure keyvalue outputEslam reda ragheb via GitGitGadget, Feb 27, 2026
  53. 11/11 repo: refine path keys for repo infoEslam reda ragheb via GitGitGadget, Feb 27, 2026
  54. Phillip WoodMar 1, 2026
  55. Lucas Seiki OshiroFeb 27, 2026
  56. 0/6 repo info: add category/path keys and --path-formateslam reda via GitGitGadget, Mar 2, 2026
  57. 1/6 repo: introduce repo_info context plumbingEslam reda ragheb via GitGitGadget, Mar 2, 2026
  58. 2/6 repo: support category requests in repo infoEslam reda ragheb via GitGitGadget, Mar 2, 2026
  59. 3/6 repo: add path keys to repo infoEslam reda ragheb via GitGitGadget, Mar 2, 2026
  60. 4/6 repo: add --path-format for info path outputEslam reda ragheb via GitGitGadget, Mar 2, 2026
  61. 5/6 t1900: cover repo info path keys and path-formatEslam reda ragheb via GitGitGadget, Mar 2, 2026
  62. 6/6 docs: describe repo info path keysEslam reda ragheb via GitGitGadget, Mar 2, 2026
  63. Jialong WangMar 18, 2026
  64. K JayatheerthMar 19, 2026
  65. Jerry WangMar 19, 2026
  66. K JayatheerthMar 20, 2026
  67. t1900: cover repo info path keys in non-default layoutsJialong Wang, Mar 19, 2026
  68. Jialong WangMar 19, 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.