Fixing rebase rather than avoiding it

[Óscar Fuentes]

Teemu Likonen <tlikonen at iki.fi> writes:

[snip]

> So, again, I'm referring to your comments: What kind of "liberal commit
> rules" would confuse "git bisect" and perhaps not some other tool? You
> said that if one wants to use "git bisect" commits must have this
> quality of being bisectable. What kind of commits don't have this
> quality, and therefore makes "git bisect" fail even if user wants to use
> it?

I already answered that.

But maybe we could communicate better if I do the questions:

How having lots of commits that break the build or just makes the
application crash is not a hurdle for automatic bisection? How could I
teach my script to detect such cases and know that the revision that
breaks the build is not, precisely, the one that introduced the bug I'm
looking for?