monotone-commits-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-commits-diffs] Revision 88fdeb39697e1d44f420f850a594b96e98d398


From: monotone
Subject: [Monotone-commits-diffs] Revision 88fdeb39697e1d44f420f850a594b96e98d3981e
Date: Sat, 28 Nov 2009 08:09:10 +0100

-----------------------------------------------------------------
Revision: 88fdeb39697e1d44f420f850a594b96e98d3981e
Ancestor: 2fc909ede8a83686bb2722871b66296256dd9a66
Author: address@hidden
Date: 2009-11-28T07:04:58
Branch: net.venge.monotone.bisect

Added files:
        tests/bisect_linear/__driver__.lua
Added directories:
        tests/bisect_linear
Modified files:
        cmd_ws_commit.cc tests/bisect/__driver__.lua

ChangeLog: 

make bisection always end on the first bad revision

* cmd_ws_commit.cc (bisect_setup): rename to ...

  (bisect_select): ... this; change return type to void; take the current
  workspace revision id and return the next selected revision id for testing;
  take a project rather than a database for calls to describe_revision; end when
  no revisions remain but ensure the workspace is updated to the first bad
  revision; move bisection of remaining revisions here from bisect_update

  (bisect_update): add an operator<< for bisect::type messaging; warn on
  redundant bisect information and fail on conflicting bisect information; move
  bisection of remaining revisions into bisect_select; replace FIXME about
  workspace branch option with the reason for not updating it

  (bisect_status): update to call bisect_select with new arguments

* tests/bisect_linear/__driver__.lua: add another bisect test for various
  simple linear bisections

* tests/bisect/__driver__.lua: avoid conflicting bisect information on one
  revision


Attachment: txtaEofbAlYfu.txt
Description: Diff [2fc909ede8a83686bb2722871b66296256dd9a66] -> [88fdeb39697e1d44f420f850a594b96e98d3981e]


reply via email to

[Prev in Thread] Current Thread [Next in Thread]