Bisect Inconsistent State

Stephen Rasku mercurial at srasku.net
Tue Jun 1 15:48:26 UTC 2010


I am trying to use bisect to determine when a piece of code disappeared.  I
am getting the error

abort: Inconsistent state, 10263:e46c28817c73 is good and bad

after only two bisect commands.  To me this doesn't seem like it should be
possible but here are the details.

$ hg up -r 10263
1562 files updated, 0 files merged, 847 files removed, 0 files unresolved
$ hg bisect -r
$ hg bisect -g
$ hg up -r 10633
1381 files updated, 0 files merged, 1028 files removed, 0 files unresolved
$ hg bisect -b
abort: Inconsistent state, 10263:e46c28817c73 is good and bad

This is for Mercurial 1.4.3.

More details are probably needed to diagnose this.  Let me know what they
are.

...Stephen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100601/b3b2369c/attachment.html>


More information about the Mercurial mailing list