From 89f57616a8535228fe15c036a77a23a434198862 Mon Sep 17 00:00:00 2001
From: Scott Lystig Fritchie <slfritchie@snookles.com>
Date: Sun, 13 Sep 2015 17:44:23 +0900
Subject: [PATCH] Avoid some churn when both latest & newprop are none proj

---
 src/machi_chain_manager1.erl | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/machi_chain_manager1.erl b/src/machi_chain_manager1.erl
index 6a70ca5..2c6586c 100644
--- a/src/machi_chain_manager1.erl
+++ b/src/machi_chain_manager1.erl
@@ -1568,6 +1568,13 @@ react_to_env_B10(Retries, P_newprop, P_latest, LatestUnanimousP, P_current_calc,
             %% Let's try to write P_newprop and see what happens!
             react_to_env_C300(P_newprop, P_latest, S);
 
+        Rank_latest < 0 andalso Rank_newprop < 0 ->
+            ?REACT({b10, ?LINE,
+                    [{rank_latest, Rank_latest},
+                     {rank_newprop, Rank_newprop}]}),
+            %% The latest projection is none proj, so is my newprop.
+            react_to_env_A50(P_latest, [], S);
+
         Rank_latest >= Rank_newprop
         andalso
         P_latest#projection_v1.author_server /= MyName ->