Date: Wed, 2 Aug 2023 15:43:09 -0600 From: Warner Losh <imp@bsdimp.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: git@freebsd.org Subject: Re: fatal: unable to read <hash> Message-ID: <CANCZdfr5PyZdFnJ_Q199yA=AaU-9gAiQa2nHR82bKkS40H%2Bsrg@mail.gmail.com> In-Reply-To: <904p9s0n-6641-7494-q259-515pp4q313q1@yvfgf.mnoonqbm.arg> References: <orqq0n25-14pq-nn97-o85p-1p6r107s20ns@yvfgf.mnoonqbm.arg> <CANCZdfrZECPrUqk5VLNifRTdo3mr=_SxjTOvGBUAJcTHgPugaQ@mail.gmail.com> <904p9s0n-6641-7494-q259-515pp4q313q1@yvfgf.mnoonqbm.arg>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Jul 30, 2023 at 7:23 PM Bjoern A. Zeeb < bzeeb-lists@lists.zabbadoz.net> wrote: > On Tue, 25 Jul 2023, Warner Losh wrote: > > > Have you tried cloning the repo? > > % git clone freebsd-src freebsd-src.x > Cloning into 'freebsd-src.x'... > done. > Updating files: 100% (94839/94839), done. > % > > Seems to run through without trouble like that. Are you suggesting that > I might just change my .git/config on the new one to point in the right > diretions again and use the cloned one (also re-establishing the > worktrees)? > I'm saying that if Marc and you can't work out why things are bad, cloning should preserve all the branches and you won't lose any work. You could script recreating the work trees, though that's a lot of disk and gets tricky if you like to stash changes... Worst case, though, is you'd have to clone the upstream repo and the fetch branches one at a time until you found the one causing the error (well, you'd fetch the rest, but then you'd know the problem child at least). I suspect it's a dangling reference somewhere that didn't get GC'd quite right and that it's an edge case in cleanup, but fixing botched repos is way above my pay grade. Good luck and hope it all works out. And if there's anything I can do to help further, please let me know. Warner [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 30, 2023 at 7:23 PM Bjoern A. Zeeb <<a href="mailto:bzeeb-lists@lists.zabbadoz.net">bzeeb-lists@lists.zabbadoz.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 25 Jul 2023, Warner Losh wrote:<br> <br> > Have you tried cloning the repo?<br> <br> % git clone freebsd-src freebsd-src.x<br> Cloning into 'freebsd-src.x'...<br> done.<br> Updating files: 100% (94839/94839), done.<br> %<br> <br> Seems to run through without trouble like that. Are you suggesting that<br> I might just change my .git/config on the new one to point in the right<br> diretions again and use the cloned one (also re-establishing the<br> worktrees)?<br></blockquote><div><br></div><div>I'm saying that if Marc and you can't work out why things are bad, cloning</div><div>should preserve all the branches and you won't lose any work. You could</div><div>script recreating the work trees, though that's a lot of disk and gets tricky</div><div>if you like to stash changes...</div><div><br></div><div>Worst case, though, is you'd have to clone the upstream repo and the fetch</div><div>branches one at a time until you found the one causing the error (well, you'd</div><div>fetch the rest, but then you'd know the problem child at least).</div><div><br></div><div>I suspect it's a dangling reference somewhere that didn't get GC'd quite right</div><div>and that it's an edge case in cleanup, but fixing botched repos is way above</div><div>my pay grade.</div><div><br></div><div>Good luck and hope it all works out. And if there's anything I can do to help</div><div>further, please let me know.</div><div><br></div><div>Warner</div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr5PyZdFnJ_Q199yA=AaU-9gAiQa2nHR82bKkS40H%2Bsrg>