Re: git bisect enhancements?

Jon Loeliger [off-list ref] writes:

Sure.  But I'm proposing to alter the new bisection
middle point.  I don't know its status yet.  I am
just angling on hedging my bets of a "good midpoint"
choice by finding something that is likely to be
more stable than the proposed midpoint.

You could "git reset --hard <that-commit-N-up-or-down>",
compile, test and say "git bisect good" or "git bisect bad".

Even "N commits before" is not so easy.  "git reset --hard
bisect~2" would be 2 commits before what git-bisect suggested as
long as that chain in question is a single strand of pearls.  "N
commits after" is a bit harder, especially when a merge is
involved.  But you are right.  Bisect should be able to do what
you can visually do with gitk.