[$] Stochastic bisection in Git

Regressions are no fun; among other things, finding the source of aregression among thousands of changes can be a needle-in-the-haystack sortof problem. The gitbisect command can help; it is a (relatively) easy way to sift through large numbers of commits to find the one that introduces a regression. When itworks well, it can quickly point out the change that causes a specificproblem. Bisection is not a perfect tool, though; it can go badly wrong insituations where a bug cannot be reliably reproduced. In an attempt tomake bisection more useful in such cases, Jan Kara is proposing to add "stochasticbisection" support to Git.