This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-accord.git
omit 7a053792 Accord: On restart, while replying the journal the linearizability check logic found incorrect ordering and rejected startup (#191) new 0f9f201f Accord: On restart, while replying the journal the linearizability check logic found incorrect ordering and rejected startup new 4918bd61 Fix durableBefore check on replay This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7a053792) \ N -- N -- N refs/heads/trunk (4918bd61) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../java/accord/utils/ReducingIntervalMap.java | 30 ++++++---------------- 1 file changed, 8 insertions(+), 22 deletions(-) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org