All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #09; Sat, 25)
Date: Mon, 27 Oct 2025 09:40:48 +0100	[thread overview]
Message-ID: <aP8wEEZa6_DgdKwG@pks.im> (raw)
In-Reply-To: <xmqqo6pun0ml.fsf@gitster.g>

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. <eesy5qhqzi56qrzv7wlpenxag23l2zykakvpmr6p5rnak6cril@ap3rugp44bcz>
>  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

  parent reply	other threads:[~2025-10-27  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 21:16 What's cooking in git.git (Oct 2025, #09; Sat, 25) Junio C Hamano
2025-10-26 15:43 ` Jeff King
2025-10-27  8:40 ` Patrick Steinhardt [this message]
2025-10-27 14:30   ` Jeff King
2025-10-27 14:38     ` Patrick Steinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aP8wEEZa6_DgdKwG@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.