From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Antw: [EXT] Re: bug in "git fsck"?
Date: Mon, 05 Jul 2021 09:10:03 +0200 [thread overview]
Message-ID: <60E2B04B020000A100042291@gwsmtp.uni-regensburg.de> (raw)
In-Reply-To: <xmqqczs0popg.fsf@gitster.g>
>>> Junio C Hamano <gitster@pobox.com> schrieb am 02.07.2021 um 20:15 in
Nachricht
<xmqqczs0popg.fsf@gitster.g>:
> "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.
OK, so maybe I was just confused by "fsck". At it seems after committing, fsck
no longer complains.
As "EXTRACTED DIAGNOSTICS" In man git-fsck (Git 2.26.2) does not mention
"unborn" (and as it's not a common IT phrase), one could probably explain what
it means.
Regards,
Ulrich
next prev parent reply other threads:[~2021-07-05 7:10 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
2021-07-05 7:10 ` Ulrich Windl [this message]
2021-07-05 7:26 ` Antw: [EXT] " Æ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
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=60E2B04B020000A100042291@gwsmtp.uni-regensburg.de \
--to=ulrich.windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).