Re: gc.auto bug in 1.6.5.7

From: Jon Nelson <jnelson@jamponi.net>
Date: Jan 6, 2010, 22:27 UTC
Message-ID: <cccedfc61001061427k6dcb35bcw9f5b5ae0aaf52786@mail.gmail.com>
In-Reply-To: <u1EMnFha7hfr0SI0p8dEvAJML7vykSCAA6YzQd7klvze6oKChlMCLg@cipher.nrlssc.navy.mil>

On Wed, Jan 6, 2010 at 12:31 PM, Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil> wrote:

Show 13 quoted lines

> Jon Nelson wrote:
>> It would appear that there is a bug in git, at least as of 1.6.5.7, in
>> the gc command.
>> When gc.auto is non-zero, it appears to consider packfiles as "loose"
>> - this conflicts with pack.packSizeLimit, insofar as I have
>> pack.packSizeLimit set to 2M (which appears to work).  If gc.auto is,
>> say, 50 - once I exceed 50 2MB packs then gc --auto repacks *every
>> single time* it is run. This is unexpected, at least.
>
> There is also a gc.autopacklimit which controls auto-gc'ing based on
> the number of packs.  The default is 50 and it does not consider the
> pack.packSizeLimit setting when deciding whether or not to auto-gc.
> It can be raised, or it can be disabled by setting it to zero.

I disabled it entirely and that seemed to resolve the issue.  Thanks!

-- 
Jon