unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org, David Bremner <david@tethera.net>
Subject: [PATCH 6/6] lib: choose oldest message when breaking reference loops
Date: Fri, 20 Apr 2018 15:31:35 -0300	[thread overview]
Message-ID: <20180420183135.14331-7-david@tethera.net> (raw)
In-Reply-To: <20180420183135.14331-1-david@tethera.net>

This preserves a sensible thread order
---
 lib/thread.cc    | 33 ++++++++++++++++++++++++---------
 test/T050-new.sh |  1 -
 2 files changed, 24 insertions(+), 10 deletions(-)

diff --git a/lib/thread.cc b/lib/thread.cc
index dbac002f..a6dc4e5a 100644
--- a/lib/thread.cc
+++ b/lib/thread.cc
@@ -390,20 +390,18 @@ _thread_add_matched_message (notmuch_thread_t *thread,
 static void
 _resolve_thread_relationships (notmuch_thread_t *thread)
 {
-    notmuch_message_node_t *node;
+    notmuch_message_node_t *node, *first_node;
     notmuch_message_t *message, *parent;
     const char *in_reply_to;
 
-    for (node = thread->message_list->head; node; node = node->next) {
+    first_node = thread->message_list->head;
+    if (!first_node)
+	return;
+
+    for (node = first_node->next; node; node = node->next) {
 	message = node->message;
 	in_reply_to = _notmuch_message_get_in_reply_to (message);
-	/*
-	 * if we reach the end of the list without finding a top-level
-	 * message, that means the thread is a cycle (or set of
-	 * cycles) and any message can be considered top-level
-	 */
-	if ((thread->toplevel_list->head || node->next) &&
-	     in_reply_to && strlen (in_reply_to) &&
+	if (in_reply_to && strlen (in_reply_to) &&
 	    g_hash_table_lookup_extended (thread->message_hash,
 					  in_reply_to, NULL,
 					  (void **) &parent))
@@ -412,6 +410,23 @@ _resolve_thread_relationships (notmuch_thread_t *thread)
 	    _notmuch_message_list_add_message (thread->toplevel_list, message);
     }
 
+    /*
+     * if we reach the end of the list without finding a top-level
+     * message, that means the thread is a cycle (or set of cycles)
+     * and any message can be considered top-level.  Choose the oldest
+     * message, which happens to be first in our list.
+     */
+    message=first_node->message;
+    in_reply_to = _notmuch_message_get_in_reply_to (message);
+    if (thread->toplevel_list->head &&
+	in_reply_to && strlen (in_reply_to) &&
+	g_hash_table_lookup_extended (thread->message_hash,
+				      in_reply_to, NULL,
+				      (void **) &parent))
+	_notmuch_message_add_reply (parent, message);
+    else
+	_notmuch_message_list_add_message (thread->toplevel_list, message);
+
     /* XXX: After scanning through the entire list looking for parents
      * via "In-Reply-To", we should do a second pass that looks at the
      * list of messages IDs in the "References" header instead. (And
diff --git a/test/T050-new.sh b/test/T050-new.sh
index 320a7646..9025fa7a 100755
--- a/test/T050-new.sh
+++ b/test/T050-new.sh
@@ -359,7 +359,6 @@ test_begin_subtest "reference loop does not crash"
 test_expect_code 0 "notmuch show --format=json id:mid-loop-12@example.org id:mid-loop-21@example.org > OUTPUT"
 
 test_begin_subtest "reference loop ordered by date"
-test_subtest_known_broken
 threadid=$(notmuch search --output=threads  id:mid-loop-12@example.org)
 notmuch show --format=mbox $threadid | grep '^Date'  > OUTPUT
 cat <<EOF > EXPECTED
-- 
2.17.0

  parent reply	other threads:[~2018-04-20 18:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  1:46 reference loop fix and tests, v2 David Bremner
2018-04-14  1:46 ` [PATCH 1/5] test: two new messages for the 'broken' corpus David Bremner
2018-04-14 22:24   ` Tomi Ollila
2018-04-15  7:36     ` Daniel Kahn Gillmor
2018-04-14  1:46 ` [PATCH 2/5] test: add known broken test for indexing an In-Reply-To loop David Bremner
2018-04-14  1:46 ` [PATCH 3/5] lib: break reference loop by choosing arbitrary top level msg David Bremner
2018-04-15  7:38   ` Daniel Kahn Gillmor
2018-04-14  1:46 ` [PATCH 4/5] test: add second reference loop test David Bremner
2018-04-14  1:46 ` [PATCH 5/5] NEWS: add item for reference loop fix David Bremner
2018-04-20 18:31   ` v3 " David Bremner
2018-04-20 18:31     ` [PATCH 1/6] test: two new messages for the 'broken' corpus David Bremner
2018-04-20 18:31     ` [PATCH 2/6] test: add known broken test for indexing an In-Reply-To loop David Bremner
2018-04-20 18:31     ` [PATCH 3/6] lib: break reference loop by choosing arbitrary top level msg David Bremner
2018-04-20 18:31     ` [PATCH 4/6] NEWS: add item for reference loop fix David Bremner
2018-04-20 18:31     ` [PATCH 5/6] test: add known broken test for thread ordering from a loop David Bremner
2018-04-20 18:31     ` David Bremner [this message]
2018-04-21 17:53       ` [PATCH 6/6] lib: choose oldest message when breaking reference loops Tomi Ollila
2018-04-25  1:52         ` David Bremner
2018-04-25 11:48           ` Tomi Ollila
2018-04-25 20:41 ` reference loop fix and tests, v2 David Bremner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180420183135.14331-7-david@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).