Antw: [EXT] Re: bug in "git fsck"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>> Junio C Hamano <gitster@xxxxxxxxx> schrieb am 02.07.2021 um 20:15 in
Nachricht
<xmqqczs0popg.fsf@gitster.g>:
> "Ulrich Windl" <Ulrich.Windl@xxxxxx‑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






[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux