|
3.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:264
|
|
4.
|
|
|
This command uses subcommands to implement the search, each
of which changes the state of the bisection. The
subcommands are:
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:272
|
|
5.
|
|
|
brz bisect start
Start a bisect, possibly clearing out a previous bisect.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:276
|
|
6.
|
|
|
brz bisect yes [-r rev]
The specified revision (or the current revision, if not given)
has the characteristic we're looking for,
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:279
|
|
7.
|
|
|
brz bisect no [-r rev]
The specified revision (or the current revision, if not given)
does not have the characteristic we're looking for,
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:283
|
|
8.
|
|
|
brz bisect move -r rev
Switch to a different revision manually. Use if the bisect
algorithm chooses a revision that is not suitable. Try to
move as little as possible.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:287
|
|
9.
|
|
|
brz bisect reset
Clear out a bisection in progress.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:292
|
|
10.
|
|
|
brz bisect log [-o file]
Output a log of the current bisection to standard output, or
to the specified file.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:295
|
|
11.
|
|
|
brz bisect replay <logfile>
Replay a previously-saved bisect log, forgetting any bisection
that might be in progress.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:299
|
|
12.
|
|
|
brz bisect run <script>
Bisect automatically using <script> to determine 'yes' or 'no'.
<script> should exit with:
0 for yes
125 for unknown (like build failed so we could not test)
anything else for no
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
breezy/bisect.py:303
|