git bisect bad @

From: Ramkumar Ramachandra <r@artagnon.com>
Date: Jan 9, 2022, 19:29 UTC
Message-ID: <1edfc6ff-4db8-447f-9eb7-85843258a286@www.fastmail.com>

Hi,

I bumped my head thrice (yes, thrice!) by using `git bisect bad @`. The error displayed to me at the end of one run was the following:

  Cela signifie que le bogue été corrigé entre ea3595845f5013359b2ba4402f948e454350a74c et 
  [2e100906d5d0c276335665ffefedb906d21165ca ea3595845f5013359b2ba4402f948e454350a74c].
  error: la bissection a échoué : 'git bisect--helper --bisect-state (null)' a retourné le code erreur -3

After the third attempt, I realized: ah yes, computers aren't magic; git-bisect.sh is basically a stupid shell script (no offense!).

Perhaps git-bisect.sh can ref-parse the arguments before starting its work? Agreed, none of the refs are expected to change during its operation, with the exception of the sneaky `@`.

Bonne année, Ram