From: Jeff King <peff@peff.net>
To: "Dale R. Worley" <worley@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Apparent bug in git-gc
Date: Mon, 15 Sep 2014 20:30:47 -0400 [thread overview]
Message-ID: <20140916003046.GE5019@peff.net> (raw)
In-Reply-To: <201409152334.s8FNY33M032615@hobgoblin.ariadne.com>
On Mon, Sep 15, 2014 at 07:34:03PM -0400, Dale R. Worley wrote:
> I have an 11 GB repository. It passes git-fsck (though with a number
> of dangling objects). But when I run git-gc on it, the file
> refs/heads/master disappears.
That's the expected behavior. Gc runs "git pack-refs", which puts an
entry into packed-refs and prunes the loose ref.
> Since HEAD points to refs/heads/master, this makes the repository
> unusable.
Unusable how? Does `git rev-parse refs/heads/master` still produce a
sha1? Does `git rev-parse HEAD`? If not, then that is definitely a bug.
-Peff
next prev parent reply other threads:[~2014-09-16 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 23:34 Apparent bug in git-gc Dale R. Worley
2014-09-16 0:30 ` Jeff King [this message]
2014-09-16 18:09 ` Dale R. Worley
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=20140916003046.GE5019@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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).