From: Patrick Steinhardt Date: Mon, 27 Oct 2025 08:40:48 GMT Subject: Re: What's cooking in git.git (Oct 2025, #09; Sat, 25) Message-ID: In-Reply-To: On Sat, Oct 25, 2025 at 02:16:02PM -0700, Junio C Hamano wrote: > * jt/repo-structure (2025-10-21) 7 commits > - builtin/repo: add progress meter for structure stats > - builtin/repo: add keyvalue and nul format for structure stats > - builtin/repo: add object counts in structure output > - builtin/repo: introduce structure subcommand > - ref-filter: export ref_kind_from_refname() > - ref-filter: allow NULL filter pattern > - builtin/repo: rename repo_info() to cmd_repo_info() > (this branch is used by kn/refs-optim-cleanup and ps/ref-peeled-tags.) > > "git repo structure", a new command. > > Will merge to 'next'? > cf. > source: <20251021182601.2687284-1-jltobler@gmail.com> The series is ready to go from my perspective. > * ps/maintenance-geometric (2025-10-23) 11 commits > - builtin/maintenance: introduce "geometric" strategy > - builtin/maintenance: make "gc" strategy accessible > - builtin/maintenance: extend "maintenance.strategy" to manual maintenance > - builtin/maintenance: run maintenance tasks depending on type > - builtin/maintenance: improve readability of strategies > - builtin/maintenance: don't silently ignore invalid strategy > - builtin/maintenance: make the geometric factor configurable > - builtin/maintenance: introduce "geometric-repack" task > - builtin/gc: make `too_many_loose_objects()` reusable without GC config > - builtin/gc: remove global `repack` variable > - Merge branch 'tb/incremental-midx-part-3.1' into ps/maintenance-geometric > (this branch uses tb/incremental-midx-part-3.1.) > > "git maintenance" command learns the "geometric" strategy where it > avoids doing maintenance tasks that rebuilds everything from > scratch. > > Will merge to 'next'. > source: <20251024-pks-maintenance-geometric-strategy-v3-0-9b5b3bdb4387@pks.im> Note that I've sent a minor reroll to address a CI flake that Peff reported in [1]. I don't think that we need to fix regeneration of the MIDX for now, as this is not a new problem. But it's something that we may want to address in the future so that we don't regenerate the MIDX in case we know it won't change anyway. Thanks! [1]: <20251025191550.GA279793@coredump.intra.peff.net> Patrick