Date: Mon, 7 Aug 2023 09:17:45 -0400 From: Marc Branchaud <marcnarc@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: git@freebsd.org Subject: Re: fatal: unable to read <hash> Message-ID: <ddc5e4c5-a11f-52c8-5347-949f12787a6a@gmail.com> In-Reply-To: <qo552875-521o-5364-3sor-3qn06p48op49@yvfgf.mnoonqbm.arg> References: <orqq0n25-14pq-nn97-o85p-1p6r107s20ns@yvfgf.mnoonqbm.arg> <80c39b3e-9013-22c0-286d-a0ccd05dc21a@gmail.com> <r5oq8n6o-82o7-0q0o-on18-1nso4r35q24r@yvfgf.mnoonqbm.arg> <22663d4f-df74-e343-c182-64705ec59f5b@gmail.com> <qo552875-521o-5364-3sor-3qn06p48op49@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-08-07 01:18, Bjoern A. Zeeb wrote: > > % git fsck --name-objects --connectivity-only --no-dangling > error: b9cdc058e6eb1b3d8b5e29ad9b911d3da98f65a7: invalid sha1 pointer in > resolve-undo of .git/worktrees/bz_maxmodname_D32383/index > Checking connectivity: 4743571, done. > Verifying commits in commit graph: 100% (384308/384308), done. > > The good news upfront; I could ditch that worktree and branch if that > will fix things. It has follow-up work to the 2021 things but I have > a copy of that outside that git tree (I love patch files in port trees :) If you no longer need the bz_maxmodname_D32383 worktree, then it sounds like the easiest solution would be deleting it -- by running git worktree remove bz_maxmodname_D32383 in your "main" repo (which you created with "git clone"). (The bz_maxmodname_D32383 branch seems to be OK, according to fsck.) M.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ddc5e4c5-a11f-52c8-5347-949f12787a6a>