Re: bug in "git fsck"?

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 5, 2021, 19:52 UTC
Message-ID: <xmqq8s2kmtco.fsf@gitster.g>
In-Reply-To: <52847a99-db7c-9634-b3b1-fd9b1342bc32@web.de>

René Scharfe <l.s.r@web.de> writes:

> True, but the scenario described on StackOverflow is a bit different.
> Commits were filtered out, and branches still pointing to them cannot
> be deleted with "git branch -d" or "git branch -D".  Git fsck only
> reports them.

I have a feeling that the "filtering out" process shouldn't leave these stale branches hanging around in the first place (in other words, it's the job of such a tool that deliberately "corrupts" the repository to remove these branches, so that the user won't have to).

But I agree that it should be easy to recover from such a deliberate repository corruption.