From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] rebase: ignore failures from "gc --auto"
Date: Wed, 13 Jan 2016 13:50:52 -0500 [thread overview]
Message-ID: <20160113185052.GA5786@sigill.intra.peff.net> (raw)
In-Reply-To: <20160113184718.GA5647@sigill.intra.peff.net>
On Wed, Jan 13, 2016 at 01:47:18PM -0500, Jeff King wrote:
> This bit me just now. The real blocker was "you have too many loose
> objects, run 'git prune'" left in the gc.log file.
Which was of course annoying in itself. I was running a scripted set of
rebases, so even with this fix, my terminal got spammed with the
"whoops, we can't auto-gc" message over and over.
The worst part is that when I looked at .git/objects, there were a lot
of objects, but most of them could be cleaned up! I wonder if
too_many_loose_objects() should take into account the prune time of the
objects it finds. I also wonder how I got into that situation, since
that check should come right _after_ we've finished running "gc". I
wonder if I had two backgrounded auto-gc's racing or something.
-Peff
next prev parent reply other threads:[~2016-01-13 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 18:47 [PATCH] rebase: ignore failures from "gc --auto" Jeff King
2016-01-13 18:50 ` Jeff King [this message]
2016-01-13 19:40 ` Rodrigo Campos
2016-01-13 20:12 ` Jeff King
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=20160113185052.GA5786@sigill.intra.peff.net \
--to=peff@peff.net \
--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).