Re: fatal: unable to read <hash>

From: Marc Branchaud <marcnarc_at_gmail.com>
Date: Mon, 07 Aug 2023 13:17:45 UTC 
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.