From: Jens Axboe <jens.axboe@oracle.com>
To: git@vger.kernel.org
Subject: auto gc
Date: Thu, 15 Nov 2007 09:10:27 +0100 [thread overview]
Message-ID: <20071115081025.GC638@kernel.dk> (raw)
Hi,
I've noticed that recent git versions, in a supposedly helpful fashion,
run garbage collection automatically after a pull if it deems it
necessary:
[...]
Resolving 556 deltas...
100% (556/556) done
Updating 9418d5d..99fee6d
Fast forward
Packing your repository for optimum performance. You may also
run "git gc" manually. See "git help gc" for more information.
Generating pack...
[...]
This is extremely annoying behaviour! If I'm on battery or just in a bit
of a hurry, I defeinitely don't want git second guessing me and deciding
that it's time to run git gc.
I'd suggest just printing a hint that running git gc would increase
performance, doing it automatically is definitely bad style (even more
so when then yet again changed git refs layout even breaks old scripts,
when git gc has run).
--
Jens Axboe
next reply other threads:[~2007-11-15 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 8:10 Jens Axboe [this message]
2007-11-15 8:20 ` auto gc Shawn O. Pearce
2007-11-15 8:28 ` Jens Axboe
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=20071115081025.GC638@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=git@vger.kernel.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).