git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Patrick Steinhardt <ps@pks.im>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #09; Sat, 25)
Date: Mon, 27 Oct 2025 10:30:30 -0400	[thread overview]
Message-ID: <20251027143030.GC2758515@coredump.intra.peff.net> (raw)
In-Reply-To: <aP8wEEZa6_DgdKwG@pks.im>

On Mon, Oct 27, 2025 at 09:40:48AM +0100, Patrick Steinhardt wrote:

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

Ah, sorry, I hadn't seen your re-roll when I wrote my other response.
What you wrote in v4 looks like a reasonable band-aid to me.

-Peff


  reply	other threads:[~2025-10-27 14:44 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
2025-10-27 14:30   ` Jeff King [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20251027143030.GC2758515@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).