Re: git gc does not clean tmp_pack* files

From: Jeff King <peff@peff.net>
Date: Dec 28, 2024, 19:44 UTC
Message-ID: <20241228194428.GB1535629@coredump.intra.peff.net>
In-Reply-To: <CADMKT2_QonR_XbZ5297Df34FrrTpbJp04Qy5BGjPb_Ov=uFF4A@mail.gmail.com>

On Fri, Dec 20, 2024 at 05:17:50PM -0800, Boomman wrote:

Show 9 quoted lines

> For me, two "git gc" on a same repo fail to run:
> fatal: gc is already running on machine 'WIN-blah' pid 40304 (use
> --force if not)
> 
> If you're already colliding on this, then I don't see why you can't
> use a normal looking name without a randomized string like
> "tmp_garbagecollecting", so that each execution would at least
> overwrite the same location. In this case --force could append _1
> probably.

git-gc is not the only thing that writes packs. There might be simultaneous packs written by incoming pushes or fetches, for example.

-Peff