#
#
# patch "rcs_import.cc"
#  from [c2f916be9c2f1abb1e0fb9fd94fe4f7ffe01d565]
#    to [3e3a17366f077b8ea1002018086d12ad4ec6e78a]
#
============================================================
--- rcs_import.cc	c2f916be9c2f1abb1e0fb9fd94fe4f7ffe01d565
+++ rcs_import.cc	3e3a17366f077b8ea1002018086d12ad4ec6e78a
@@ -3662,17 +3662,6 @@ split_cycle(cvs_history & cvs, vector<cv
           upper_bound = t2_lower_bound;
           L(FL("  blob: %d:\tcan easily split by timestamp.") % *cc);
         }
-      else if (t2_upper_bound < t3_lower_bound)
-        {
-          // I've so far never seen this, and it's very probable this
-          // cannot happen at all logically. However, it's trivial
-          // supporting this case, so I'm just emitting a warning here.
-          W(F("Oh, still strange timestamps?!? Please show this repo "
-              "to <address@hidden>!"));
-          lower_bound = t2_upper_bound;
-          upper_bound = t3_lower_bound;
-          L(FL("  blob: %d:\tstrange, but can split by timestamp.") % *cc);
-        }
       else
         {
           // The timestamps of type 2 and type 3 events are overlapping, so