[issue2690] bisect stops too early

[benallard]

New submission from benallard <benoit at aeteurope.nl>:

When the result of a bisection is a merge changeset and that one of the
parents is outside of the initial range, mercurial considers the bisection
done, although giving a useful hint on what should be the next changeset to
check.

(Hint introduced by 1ef9b0b5efec)

Wouldn't it be better to extend the initial range, update to this hinted
revision and continue the bisect ?

(I first reported this as a thg issue
(https://bitbucket.org/tortoisehg/thg/issue/305))

----------
messages: 15580
nosy: benallard, djc
priority: bug
status: unread
title: bisect stops too early

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2690>
____________________________________________________