Getting the right root mail of the thread

diff --git a/91/5d33444836c9874b750b2a5409fadb51a84489 b/91/5d33444836c9874b750b2a5409fadb51a84489
new file mode 100644 (file)
index 0000000..ca663c8
--- /dev/null
+++ b/91/5d33444836c9874b750b2a5409fadb51a84489
@@ -0,0 +1,99 @@
+Return-Path: <felipe.contreras@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id E7BA8431FAF\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:25:35 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id K4HUy+sdW2dz for <notmuch@notmuchmail.org>;\r
+       Sat,  2 Nov 2013 06:25:30 -0700 (PDT)\r
+Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com\r
+       [209.85.214.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 38257431FC3\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:25:30 -0700 (PDT)\r
+Received: by mail-ob0-f174.google.com with SMTP id vb8so5622559obc.33\r
+       for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 06:25:29 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=date:from:to:cc:message-id:subject:mime-version:content-type\r
+       :content-transfer-encoding;\r
+       bh=PDy/Q7x/ERxiHqh2jiQkzOuLBMsuv1oW1KlMkQqKsUA=;\r
+       b=00lT7i1bgO92U8gTOtkUpRU9QoA5Or7/ER/gtUod2W8IK7UVeRtVQYijDv9lfDPdme\r
+       RK4Q7F88ej7GaNZdQ/ZNLLVx7jfpRpUuuZdKja0h1OKsq9btMrb6yPw1KaYILTyTuTF8\r
+       nwF5ERd3M+dKNKEFTeYGTc163h5RjFGEVWQtYvdaI9kl0UPRFuaOcKHp3wENhPV4huOE\r
+       T+E0k3dE2DdO+RVJHHhvSUi2oAztTu238O8aXPC5iBcAW4KXq7JSjvMlw3ybwhdvHDfU\r
+       eqVoap8lcLDyuETWLj/MkWrZL1kUt72p1U+OzrQmeuyu5CpO0OetOGOeNyYk2DQxCFA2\r
+       8G4Q==\r
+X-Received: by 10.60.116.230 with SMTP id jz6mr6498125oeb.21.1383398729501;\r
+       Sat, 02 Nov 2013 06:25:29 -0700 (PDT)\r
+Received: from localhost (187-162-140-241.static.axtel.net. [187.162.140.241])\r
+       by mx.google.com with ESMTPSA id\r
+       tz10sm10494016obc.10.2013.11.02.06.25.27\r
+       for <notmuch@notmuchmail.org>\r
+       (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+       Sat, 02 Nov 2013 06:25:28 -0700 (PDT)\r
+Date: Sat, 2 Nov 2013 07:08:14 -0600\r
+From: Felipe Contreras <felipe.contreras@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Cc: \r
+Message-Id: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
+Subject: Getting the right root mail of the thread\r
+Mime-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: 7bit\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 02 Nov 2013 13:25:39 -0000\r
+\r
+Hi,\r
+\r
+I often wondered why when browsing threads, I often see a message that doesn't\r
+describe at all the thread, for example:\r
+\r
+  notmuch search ...\r
+  thread:000000000000826a 18 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 44/44]\r
+\r
+I can reverse the order of the search:\r
+\r
+  notmuch search --sort=oldest-first\r
+  thread:000000000000826a 23 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 00/44]\r
+\r
+Then I get the correct summary, but now the order of the search is the other\r
+way around, and there doesn't seem to be a way to specify the order of the\r
+messages independently of the order of the threads.\r
+\r
+Either way this doesn't make any sense to me. Each thread has a single origin\r
+mail, why would anybody would like to show a message other than that while\r
+displaying the summary of the tread? Even more, why isn't there an option to\r
+fetch that information easily?\r
+\r
+I am forced to get the list of messages, and then grab the first one, even\r
+though it's not efficient, probably unnecessary, and potentiall wrong. For\r
+example, it's possible that multiple mails arrived at the same time, then how\r
+am I supposed to display the one that originated the thread?\r
+\r
+I think there should be a way to get the root mail of a thread, irrespective of\r
+the search order.\r
+\r
+Cheers.\r
+\r
+-- \r
+Felipe Contreras\r