From: "René Scharfe" <l.s.r@web.de>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: git@vger.kernel.org
Subject: Re: Antw: [EXT] Re: bug in "git fsck"?
Date: Mon, 5 Jul 2021 16:44:50 +0200 [thread overview]
Message-ID: <77655a4e-8c39-5ccc-71af-d2d8684bf208@web.de> (raw)
In-Reply-To: <60E2B7FB020000A1000422A0@gwsmtp.uni-regensburg.de>
Am 05.07.21 um 09:42 schrieb Ulrich Windl:
>>>> René Scharfe <l.s.r@web.de> schrieb am 03.07.2021 um 22:03 in Nachricht
> <52847a99-db7c-9634-b3b1-fd9b1342bc32@web.de>:
>> Am 02.07.21 um 20:15 schrieb Junio C Hamano:
>>> "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> writes:
>>>
>>>> I was wondering whether git fsck should be able to cleanup
>>>> orphaned branches ("HEAD points to an unborn branch") as described
>>>> in https://stackoverflow.com/q/68226081/6607497 It seems I can fix
>>>> it be editing files in the repository, but I feed that's not the
>>>> way it should be.
>>>
>>> HEAD pointing at an unborn branch is not even a corruption, isn't
>>> it?
>>>
>>> $ rm -rf trash && git init trash
>>>
>>> would point HEAD at an unborn one, ready to be used.
>>
>> 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.
>>
>> You *can* overwrite them using "git branch --force foo" and then
>> "git branch -d foo" works.
>
> Would it be OK to force the branch to any commit (e.g.: "master"), relying on
> the fact that any reference (read: "master") to that commit will prevent actual
> removal of the commit?
Yes, any valid commit would do. This turns dangling branches into
normal delete-able ones. Other branches are unaffected.
René
next prev parent reply other threads:[~2021-07-05 14:44 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 [this message]
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
2021-07-05 7:10 ` Antw: [EXT] " 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=77655a4e-8c39-5ccc-71af-d2d8684bf208@web.de \
--to=l.s.r@web.de \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
/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).