lp:~naesten/bzr-bisect/683822-bisect-start-range-argument

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:bzr-bisect

Bazaar Developers: Pending requested 2012-09-16

Diff: 252 lines (+99/-18)

2 files modified

cmds.py (+62/-18)
tests.py (+37/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #683822: bisect start should take a range argument

Wishlist

Triaged

Link a bug report

Related blueprints

91. By Samuel Bronson on 2012-09-21

Add some debug output (mostly log-only).

90. By Samuel Bronson on 2012-09-19

Add a test for "bzr bisect run -r".

89. By Samuel Bronson on 2012-09-19

Reverse polarity of "start -r" and "run -r".

Now it matches the "run" commands's return-value handling.

88. By Samuel Bronson on 2012-09-18

Merge lp:~jeff-licquia/bzr-bisect/yesno

This gives "yes" and "no" equal standing again.

87. By Samuel Bronson on 2012-09-18

Roll back my test changes; later, I'll add some tests just for this.

86. By Samuel Bronson on 2012-09-16

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 on 2012-09-15

Cleanup option handling preperatory to implementing bug 683822.

84. By Jelmer Vernooij on 2012-08-03

Merge fix for compatibility with newer versions of bzr from Thomi.

83. By Jelmer Vernooij on 2011-11-25

Merge support for lazy loading.

82. By Jelmer Vernooij on 2011-08-14

Add basic installation instructions.