From: Pierre Ossman Date: Thu, 20 Feb 2025 08:26:38 GMT Subject: Re: [External] git keeps recreating packs, exploding backup increments Message-ID: In-Reply-To: On 20/02/2025 04:03, Han Young wrote: > On Wed, Feb 19, 2025 at 5:58 PM Pierre Ossman wrote: >> We tried gc.bigPackThreshold in the hope it would force it to reuse >> packs better. But all we got instead was duplication. It still creates >> new packs with everything. It just stopped removing the old ones. > > Is the repo partially cloned? git-repack will always pack promisor > packs even if it's a keep pack. This patch would fix it > https://lore.kernel.org/git/2728513.vuYhMxLoTh@mintaka.ncbr.muni.cz/ > Yes, the big offender is often partially cloned. So that could be part of it, thanks. But we're seeing it in other repositories as well. E.g. I have a long-lived TigerVNC repository where the biggest pack file is just one week old. In that case, it's merely 21 MiB, so it's not a practical issue. But it does show that git keeps replacing it. Anything I/we can do to shed more light on the issue? Regards, -- Pierre Ossman Software Development Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linköping https://facebook.com/ThinLinc Phone: +46-13-214600 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?