From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: auto gc again
Date: Tue, 18 Mar 2008 19:24:21 +0100 [thread overview]
Message-ID: <20080318182421.GI17940@kernel.dk> (raw)
In-Reply-To: <20080318181948.GH17940@kernel.dk>
On Tue, Mar 18 2008, Jens Axboe wrote:
> On Tue, Mar 18 2008, Linus Torvalds wrote:
> >
> >
> > 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
axboe@carl:~/git/linux-2.6-block> git count-objects
901 objects, 6448 kilobytes
xboe@carl:~/git/linux-2.6-block> git pull
remote: Counting objects: 320, done.
remote: Compressing objects: 100% (43/43), done.
remote: Total 214 (delta 171), reused 214 (delta 171)
Receiving objects: 100% (214/214), 31.78 KiB, done.
Resolving deltas: 100% (171/171), completed with 68 local objects.
From ssh://git.kernel.dk/data/git/linux-2.6-block
bde4f8f..f920bb6 master -> origin/master
Updating bde4f8f..f920bb6
Fast forward
Auto packing your repository for optimum performance. You may also
run "git gc" manually. See "git help gc" for more information.
^C
So 901 objects, pulled 68 objects. And auto gc kicks in. WTF? The git
before was from probably a week ago, this above run was done with git
just updated.
git version 1.5.5.rc0.6.gdeda
--
Jens Axboe
next prev parent reply other threads:[~2008-03-19 19:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 18:01 auto gc again Jens Axboe
2008-03-18 18:14 ` Linus Torvalds
2008-03-18 18:19 ` Jens Axboe
2008-03-18 18:24 ` Jens Axboe [this message]
2008-03-18 18:33 ` Linus Torvalds
2008-03-18 18:39 ` Jens Axboe
2008-03-19 20:22 ` Johannes Schindelin
2008-03-19 21:14 ` Jens Axboe
2008-03-19 21:44 ` Johannes Schindelin
2008-03-20 6:00 ` Jens Axboe
2008-03-19 20:37 ` Nicolas Pitre
2008-03-19 21:17 ` Jens Axboe
2008-03-19 23:05 ` Nicolas Pitre
2008-03-20 7:40 ` Jens Axboe
2008-03-20 7:55 ` Junio C Hamano
2008-03-20 17:31 ` Jens Axboe
2008-03-19 21:27 ` Brandon Casey
2008-03-19 21:53 ` [PATCH] builtin-gc.c: allow disabling all auto-gc'ing by assigning 0 to gc.auto Brandon Casey
2008-03-20 7:08 ` Teemu Likonen
2008-03-19 22:56 ` auto gc again Nicolas Pitre
2008-03-20 6:01 ` Jens Axboe
2008-03-19 21:27 ` Junio C Hamano
2008-03-19 21:52 ` Linus Torvalds
2008-03-19 22:28 ` Junio C Hamano
2008-03-19 23:16 ` Nicolas Pitre
2008-03-19 23:25 ` Junio C Hamano
2008-03-20 3:13 ` Nicolas Pitre
2008-03-20 4:09 ` Junio C Hamano
2008-03-20 4:40 ` Nicolas Pitre
2008-03-20 4:49 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080318182421.GI17940@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).