Re: [PATCH v2 0/2] builtin/maintenance: improve heuristic for "rerere gc"

From: Thomas Bachem <mail@thomasbachem.com>
Date: Sep 4, 2026, 16:53 UTC
Message-ID: <CAA0xjtrL8DJp61jp7s0L6L+RviwQz=-PEo7qZvCTh+8nT2cdfw@mail.gmail.com>
In-Reply-To: <xmqqld9h56yt.fsf@gitster.g>

Hi Junio,

On 04/09/2026 18:14, Junio C Hamano wrote:

> So the two-patch series is not about what happens when two "rerere
> gc" trigger in quick successions, and even with the "improve"d
> heuristic, the second "rerere gc" would fail the same way when when
> another one is already running?

Right, Patrick's series only makes the gc run less often. The lock itself is the subject of

  [PATCH v3] rerere: keep a background gc from killing a rebase
  <pull.2214.v3.git.1788537081930.gitgitgadget@gmail.com>

where setup_rerere() waits rerere.lockTimeout for it and then goes on without rerere, and a gc that finds it held gives up at once.

Thomas