From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: Antw: [EXT] Re: bug in "git fsck"?
Date: Mon, 05 Jul 2021 09:26:49 +0200 [thread overview]
Message-ID: <87fswt6wxb.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <60E2B04B020000A100042291@gwsmtp.uni-regensburg.de>
On Mon, Jul 05 2021, Ulrich Windl wrote:
>>>> 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.
FWIW you're completely right about the unstated point that fsck's error
messages/reporting is pretty bad. I've been trying to fix some of it up
recently (including one hopefully soon-to-land series).
It has a bunch of output that's overly verbose, and other complaints
where it's not clear if they're actionable or not (e.g. what you
mentioned), or whether it's even a problem.
If I create an ext4 filesystem and run fsck on it it's not going to
complain that there's no files yet, so it's a bit silly that fsck
complains about a freshly git-init'd repo.
next prev parent reply other threads:[~2021-07-05 7:29 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 ` Antw: [EXT] " Ulrich Windl
2021-07-05 7:26 ` Ævar Arnfjörð Bjarmason [this message]
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=87fswt6wxb.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=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.
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.