From: Andreas Schwab <schwab@suse.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: git gc complains about "unable to read $oid" but git fsck finds no problems
Date: Thu, 01 Jun 2023 12:38:16 +0200 [thread overview]
Message-ID: <mvmbkhza2nb.fsf@suse.de> (raw)
In-Reply-To: <xmqqsfbba42c.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 01 Jun 2023 19:07:39 +0900")
On Jun 01 2023, Junio C Hamano wrote:
> I vaguely recall there was a recent threaad discussing fsck and
> normal codepath doing different checks.
>
> Does this look similar to what you have? (sorry, I am running out
> of gas tonight to dig deeply myself).
>
> https://lore.kernel.org/git/20230330181716.GA3286761@coredump.intra.peff.net/
Thanks, that indeed looks similar.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2023-06-01 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 10:00 git gc complains about "unable to read $oid" but git fsck finds no problems Andreas Schwab
2023-06-01 10:07 ` Junio C Hamano
2023-06-01 10:38 ` Andreas Schwab [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmbkhza2nb.fsf@suse.de \
--to=schwab@suse.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).