From e1a46d85fb18081f88a5c9e9fcda9d2200706362 Mon Sep 17 00:00:00 2001
From: Michael Kirk <michael@signal.org>
Date: Thu, 20 Sep 2018 16:25:54 -0600
Subject: [PATCH] investigation shows we don't use this timestamp for call
 error messages

---
 SignalServiceKit/src/Messages/OWSOutgoingCallMessage.m | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/SignalServiceKit/src/Messages/OWSOutgoingCallMessage.m b/SignalServiceKit/src/Messages/OWSOutgoingCallMessage.m
index ef8b39350..d32f1ca58 100644
--- a/SignalServiceKit/src/Messages/OWSOutgoingCallMessage.m
+++ b/SignalServiceKit/src/Messages/OWSOutgoingCallMessage.m
@@ -15,9 +15,7 @@ NS_ASSUME_NONNULL_BEGIN
 
 - (instancetype)initWithThread:(TSThread *)thread
 {
-    // MJK TODO - investigate this.
-    // These records aren't saved, but their timestamp is used in the event
-    // of a failing message send to insert the error at the appropriate place.
+    // MJK TODO - safe to remove senderTimestamp
     self = [super initOutgoingMessageWithTimestamp:[NSDate ows_millisecondTimeStamp]
                                           inThread:thread
                                        messageBody:nil