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:19:48 +0100 [thread overview]
Message-ID: <20080318181948.GH17940@kernel.dk> (raw)
In-Reply-To: <alpine.LFD.1.00.0803181112270.3020@woody.linux-foundation.org>
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
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
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 [this message]
2008-03-18 18:24 ` Jens Axboe
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=20080318181948.GH17940@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).