On Thu, Oct 19, 2017 at 8:16 PM, Jeff King <p...@peff.net> wrote: > On Thu, Oct 19, 2017 at 06:43:57PM -0700, Stefan Beller wrote:
> > So that's the right immediate workaround (and hoping there was nothing > valuable in that worktree!). How would I know? ;) Without the commit available I do not even know if the code there is well reasoned about. (My commit messages usually tell my future self how much thought I put into the code) > >> Any idea which direction we need to heading for a real fix? > > If my analysis above is correct, then it's already fixed. You just had > leftover corruption. Well fetching yesterday worked and the commit in question is from 8/23, the merge 8a044c7f1d56cef657be342e40de0795d688e882 occurred 9/18, so I suspect there is something else at play. (I do not remember having a gc between yesterday and today. Though maybe one in the background?) I am curious how you can have a worktree owned by multiple repositories [1] (?). Thanks, Stefan
