Re: [PATCH v2 0/5] builtin/repo: include largest object information

From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date: Feb 28, 2026, 23:43 UTC
Message-ID: <EB04AA40-87BA-41D9-B2DC-92E87FACEB54@gmail.com>
In-Reply-To: <20260223174120.2356504-1-jltobler@gmail.com>

Hi, Justin!

I was trying this patch series and I noticed that it took more time to run than before. In my machine, I tested it with the Git repository itself and it took 6s to run, while it took 3s to run in the current master [1].

I understand the reason and I don't think we could avoid that, but I'm wondering if wouldn't be nice to have some way to only retrieve the "lighter" data (perhaps a flag, or something like the keys in git-repo-info).

Thanks!

[1] 2cc7191751 (The 8th batch, 2026-02-27)

$ 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.