Hi,
Although "git bisect" is called, well, bisect, it would be nice to
have other modes.
* A completely linear version - check every version. Particularly
useful after rebasing to make sure all the commits still compile.
* An allow-for-mistakes-bisect. This would use a bisection technique
that would allow for a minimum of 1 mistake when marking a commit good
or bad. This point isn't particularly to help those with fat fingers,
but for bugs that are subtle and for bugs that are caused by multiple
commits. (I can go into the details of how to do such a bisect
later).
* An exponential back-off. Typically I know that HEAD is broken, and
I don't know when it used to work. It would be nice to exponentially
go back through the commits to find the first working commit, then
bisect from there.
Before I start working on the code for any of these, do people like
this? Would this fit into the 'git bisect' command?
John