From: Jeff King <peff@peff.net>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: Recovering from gc errors
Date: Wed, 15 Nov 2017 00:19:08 +0000 [thread overview]
Message-ID: <20171115001907.vno7fo4t4bglh35n@sigill.intra.peff.net> (raw)
In-Reply-To: <3af0f8cc-09f3-bcf2-04c8-f076e0ddcea2@xiplink.com>
On Tue, Nov 14, 2017 at 10:39:31AM -0500, Marc Branchaud wrote:
> > rm -rf .git/logs
>
> Unfortunately, removing the logs directory does not fix "git gc". So I
> restored it.
>
> However I did find all of the bad SHAs in the HEAD logs of four of my
> worktrees.
Ah, right. There are more logs than .git/logs these days. That makes
sense.
> I'm willing to chalk this up to bugs in the early worktree code, unless one
> of the CC'd worktree developers thinks otherwise.
Perhaps fixed by acd9544a8f (revision.c: --reflog add HEAD reflog from
all worktrees, 2017-08-23). I think before then that prune/repack would
consider those objects unreachable.
-Peff
prev parent reply other threads:[~2017-11-15 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:13 Recovering from gc errors Marc Branchaud
2017-11-14 5:53 ` Jeff King
2017-11-14 15:39 ` Marc Branchaud
2017-11-14 16:48 ` Eric Sunshine
2017-11-15 0:19 ` Jeff King [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171115001907.vno7fo4t4bglh35n@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.com \
--cc=pclouds@gmail.com \
--cc=sunshine@sunshineco.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).