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

Re: [PATCH v2 0/3] refs: cleanup code around optimizations

From
Patrick Steinhardt <ps@pks.im>
Date
Oct 21, 2025, 05:16 UTC
Message-ID
<aPcXNOz7HdxfUzcC@pks.im>
In-Reply-To
<20251020-refs-code-cleanup-v2-0-f5349ed0f6a5@gmail.com>
On Mon, Oct 20, 2025 at 10:18:28AM +0200, Karthik Nayak wrote:
Show 24 quoted lines
> This is extracted from a recent series I sent [1], which I've since
> dropped to follow up with a different approach. I think these patches
> hold value individually.
> 
> They mostly cleanup code around 'git refs optimize' which was added
> recently in db0babf9b2 (Merge branch 'ms/refs-optimize', 2025-10-02).
> The code in the refs subsystem contains both 'pack-refs' and 'optimize'
> functions, which are one and the same.
> 
> This series unifies this to only retain the 'optimize' functions and
> naming, since it backend generic.
> 
> This is based on top of master 143f58ef75 (Sync with Git 2.51.1,
> 2025-10-15) with 'ps/ref-peeled-tags' merged in.
> 
> [1]: 20251010-562-add-option-to-check-if-reference-backend-needs-repacking-v1-0-c7962be584fa@gmail.com
> 
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---
> Changes in v2:
> - Squash the second commit into the first.
> - Change some variable names to also no longer refer to pack_refs.
> - Fix commit messages.
> - Link to v1: https://lore.kernel.org/r/20251015-refs-code-cleanup-v1-0-550fdd8a3b41@gmail.com
This version looks good to me. Thanks for all these cleanups!
Patrick
Previous: Karthik NayakNext: Karthik Nayak
Message 5 of 6 in “refs: cleanup code around optimizations”
  1. 0/3 refs: cleanup code around optimizationsKarthik Nayak, Oct 20, 2025
  2. 1/3 refs: move to using the '.optimize' functionsKarthik Nayak, Oct 20, 2025
  3. 2/3 refs: rename 'pack_refs_opts' to 'refs_optimize_opts'Karthik Nayak, Oct 20, 2025
  4. 3/3 t/pack-refs-tests: move the 'test_done' to calleesKarthik Nayak, Oct 20, 2025
  5. Patrick SteinhardtOct 21, 2025
  6. Karthik NayakOct 22, 2025

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.