|Version||(1, 1, 0, ‘pre’, 0)|
|Windows||Maybe (please test)|
|Mac OS X||Yes|
Support for git-style bisection.
Find an interesting commit using a binary search.
bzr bisect SUBCOMMAND [ARGS...]
|-v, --verbose||Display more information.|
|-h, --help||Show help message.|
|-q, --quiet||Only display errors and warnings.|
|--usage||Show usage message and options.|
|-o ARG, --output=ARG|
|Write log to this file.|
|-r ARG, --revision=ARG|
|See “help revisionspec” for details.|
Bisecting, in a nutshell, is a way to find the commit at which some testable change was made, such as the introduction of a bug or feature. By identifying a version which did not have the interesting change and a later version which did, a developer can test for the presence of the change at various points in the history, eventually ending up at the precise commit when the change was first introduced.
This command uses subcommands to implement the search, each of which changes the state of the bisection. The subcommands are:
Bisect automatically using <script> exit value to determine ‘yes’ or ‘no’.
|125||Unknown (e.g. build failed so we could not test)|