bisect start should take a range argument

Bug #683822 reported by Xavier (Open ERP) on 2010-12-01
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar Bisect Plugin
Wishlist
Unassigned

Bug Description

Starting up a bisection session with bzr bisect can be a bit unclear. It would be nice if bisect start took an optional revision range and bisected within that range:

* `bzr bisect start revA..revB` would be equivalent to `bzr bisect start; bzr bisect no -rrevA; bzr bisect yes -rrevB`
* `bzr bisect start revA..` would be equivalent to `bzr bisect start; bzr bisect no -rrevA`
* `bzr bisect start ..revB` would equivalent to `bzr bisect start; bzr bisect yes -rrevB`

Related branches

Gustaf Thorslund (gthorslund) wrote :

Using revisionspec syntax would probably be good here.

Currently "bzr bisect yes/no -rrevno" also changes to revno. This can be a bit annoying since it can take some time on a bigger tree. Would be better to just give a range and run at the same time.

Dr Al (abudden) wrote :

This should also work with bzr bisect run

Jelmer Vernooij (jelmer) on 2012-03-22
Changed in bzr-bisect:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers