Re: auto gc again

From: Jens Axboe <jens.axboe@oracle.com>
Date: Mar 18, 2008, 18:19 UTC
Message-ID: <20080318181948.GH17940@kernel.dk>
In-Reply-To: <alpine.LFD.1.00.0803181112270.3020@woody.linux-foundation.org>

On Tue, Mar 18 2008, Linus Torvalds wrote:

Show 12 quoted lines

> 
> 
> On Tue, 18 Mar 2008, Jens Axboe wrote:
> > 
> > Could we please PLEASE kill this auto gc thing? I've complained about
> > this in the past and disabled it through the gc.auto config entry,
> > however now git seems to be happily auto running gc even with gc.auto=0.
> > So there's probably some new magic I need to know.
> 
> Do you do something odd with your repositories? I don't even touch autogc 
> on my systems, but I have never had that thing trigger, even when I apply 
> series of patches from Andrew with hundreds of messages.

Not to my knowledge, I haven't changed anything in my setup or behaviour in ages.

> So what is it that you do to even get this behaviour in the first place?

The last few times it was:

$ git checkout master $ git branch some-test-branch $ git checkout some-test-branch $ git pull . some-devel-branch

and after that pull, I get to sit around waiting git gc. Well I don't since I ctrl-c it because it's inconvenient.

But freshly pulled repo, git auto gc is enabled. And that is my main annoyance, I just don't think that type of policy should be in there. Print the warning, include info on how to run git gc or even how to turn it on automatically. But I'll bet you that most users will NOT want auto gc. Ever.

-- 
Jens Axboe