On Mon, Mar 12, 2018 at 10:39 PM, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > Now, obviously the root cause is that the repo is corrupt through some > other bug (since fixed?), but the error message here is really bad, and > should at least say "fatal: bad object HEAD in worktree blah" or > something like that. I know. I know. I'm working on it. I hit a wall and had to re-think my approach, but I think it should be ok this time. Will be posting a series soonish, which should also fix fsck ignoring HEADs from other worktrees. -- Duy
