On Thu, Jul 19, 2018 at 12:51 AM Elijah Newren <newren@xxxxxxxxx> wrote: > > I had a user report some poor behavior of 'git gc --aggressive' on a > certain repo (which I sadly cannot share). Turns out that on this > repo, this operation takes about 60% longer and produces a pack > roughly twice the expected size. The intention was to make life better for weaker machines but definitely should not slow down beefier ones, so yes this is definitely a regression. Is it possible to share "verify-pack -v <pack file>" output of the pack produced by 2.17.0 and 2.18.0? The only sensitive info there is sha-1, which you can replace with just "SHA-1" if you want. I'm more interested in delta sizes and distribution. -- Duy