From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, git@vger.kernel.org
Subject: Re: bug in "git fsck"?
Date: Mon, 05 Jul 2021 12:52:07 -0700 [thread overview]
Message-ID: <xmqq8s2kmtco.fsf@gitster.g> (raw)
In-Reply-To: <52847a99-db7c-9634-b3b1-fd9b1342bc32@web.de> ("René Scharfe"'s message of "Sat, 3 Jul 2021 22:03:25 +0200")
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.
next prev parent reply other threads:[~2021-07-05 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 14:01 bug in "git fsck"? Ulrich Windl
2021-07-02 18:15 ` Junio C Hamano
2021-07-03 20:03 ` René Scharfe
2021-07-05 7:42 ` Antw: [EXT] " Ulrich Windl
2021-07-05 14:44 ` René Scharfe
2021-07-06 7:12 ` Ulrich Windl
2021-07-06 14:25 ` René Scharfe
2021-07-08 8:20 ` Ulrich Windl
2021-07-08 16:36 ` René Scharfe
2021-07-05 19:52 ` Junio C Hamano [this message]
2021-07-05 7:10 ` Ulrich Windl
2021-07-05 7:26 ` Ævar Arnfjörð Bjarmason
2021-07-05 7:20 ` Ulrich Windl
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=xmqq8s2kmtco.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.