Merge lp:~naesten/bzr-bisect/683822-bisect-start-range-argument into lp:bzr-bisect
Status: | Needs review | ||||
---|---|---|---|---|---|
Proposed branch: | lp:~naesten/bzr-bisect/683822-bisect-start-range-argument | ||||
Merge into: | lp:bzr-bisect | ||||
Diff against target: |
252 lines (+99/-18) 2 files modified
cmds.py (+62/-18) tests.py (+37/-0) |
||||
To merge this branch: | bzr merge lp:~naesten/bzr-bisect/683822-bisect-start-range-argument | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Bazaar Developers | Pending | ||
Review via email: mp+124565@code.launchpad.net |
Unmerged revisions
- 91. By Samuel Bronson
-
Add some debug output (mostly log-only).
- 90. By Samuel Bronson
-
Add a test for "bzr bisect run -r".
- 89. By Samuel Bronson
-
Reverse polarity of "start -r" and "run -r".
Now it matches the "run" commands's return-value handling.
- 88. By Samuel Bronson
-
Merge lp:~jeff-licquia/bzr-bisect/yesno
This gives "yes" and "no" equal standing again.
- 87. By Samuel Bronson
-
Roll back my test changes; later, I'll add some tests just for this.
- 86. By Samuel Bronson
-
Implement the "-r revA..revB" syntax for "start" and "run" suggested in bug 683822.
Quite likely this is buggy, and none of the scenareos in the test suite (some of which I converted to this syntax) are complicated enough to show this: they all seem to start by setting the bisect range to cover all revisions on the branch.
More tests would be quite useful!
- 85. By Samuel Bronson
-
Cleanup option handling preperatory to implementing bug 683822.
Unfortunately, it turns out that this doesn't match the convention used by "run" for the common case of finding when a problem was introduced :-(.