On Fri, Jan 3, 2014 at 8:18 AM, Alan W. Irwin irwin@beluga.phys.uvic.ca wrote:
On 2014-01-02 13:07-0600 Ken Thomases wrote: Just out of curiosity what would git do if you tried to do a bisect between 1.6.1 (for a case where that was "good") and the latest 1.7.x release (for a case where that was "bad"). There is obviously no direct forward development path between the two cases. Would git error out or would it automatically bisect using a development path consisting of the reverse development path back to 1.6 combined with the forward development path from there to the latest 1.7 release?
It would find a common ancestor, and have you test thie (1.6 in this case (and warn you about this). e.g. in this case:
$ git bisect start $ git bisect bad master $ git bisect good wine-1.6.1
Bisecting: a merge base must be tested [50dc4cd636cc88031e0a49697ccc9f03b398e449] Release 1.6.