Re: Getting the right root mail of the thread

diff --git a/6d/d224c7d08f9440bece44247ec7ba4f26c4558d b/6d/d224c7d08f9440bece44247ec7ba4f26c4558d
new file mode 100644 (file)
index 0000000..b8dea33
--- /dev/null
+++ b/6d/d224c7d08f9440bece44247ec7ba4f26c4558d
@@ -0,0 +1,78 @@
+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 4B96D431FD0\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 07:13:09 -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 9d2oBC3IFtj4 for <notmuch@notmuchmail.org>;\r
+       Sat,  2 Nov 2013 07:13:04 -0700 (PDT)\r
+Received: from mail-la0-f42.google.com (mail-la0-f42.google.com\r
+       [209.85.215.42]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 93C5C431FC3\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 07:13:04 -0700 (PDT)\r
+Received: by mail-la0-f42.google.com with SMTP id ea20so4238283lab.15\r
+       for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 07:13:01 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+       :cc:content-type;\r
+       bh=R4pA1gj+BPkoPnNIl4RfrlJZrWbUvd79x6AfEc8Jirk=;\r
+       b=z3Ga6aRcItd770XIcYuUK9MWG05DrTPbCs/njzIHe+OmfAz4Jp/AuoF+bTJGUjBdXP\r
+       nwuny5SotmkO6AgCkVkMt47f+QGeW4bIB7BCzMGL2GnepoeTzh5t8Cd8CvMEO07IRoKo\r
+       z0zQaku+mp+rraueBWMJqYwqCBtDkpFJk7+lYZF3FaOy3fIg8KIxFLAgjs9ECWDyvHoT\r
+       UujgCpb+coYg0rCUKfDpWXjFk5Y4janSpxXC5XepSgVjlg5Xjy4SOQt3prJOZe8iUT6z\r
+       r+mqUeaDh9LKJdypAhvjMggNGDg2lKT0GkB8di7H23koGeyFZpG/eQluHCx5rv8wNmwZ\r
+       aBog==\r
+MIME-Version: 1.0\r
+X-Received: by 10.152.45.42 with SMTP id j10mr5067931lam.15.1383401183622;\r
+       Sat, 02 Nov 2013 07:06:23 -0700 (PDT)\r
+Received: by 10.114.201.69 with HTTP; Sat, 2 Nov 2013 07:06:23 -0700 (PDT)\r
+In-Reply-To: <87zjpmoqtz.fsf@nikula.org>\r
+References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
+       <87zjpmoqtz.fsf@nikula.org>\r
+Date: Sat, 2 Nov 2013 08:06:23 -0600\r
+Message-ID:\r
+ <CAMP44s19GP0w9UTTzeos2wQXHuYLpfF74BdJpxvLy=RD16=HXg@mail.gmail.com>\r
+Subject: Re: Getting the right root mail of the thread\r
+From: Felipe Contreras <felipe.contreras@gmail.com>\r
+To: Jani Nikula <jani@nikula.org>\r
+Content-Type: text/plain; charset=UTF-8\r
+Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>\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 14:13:09 -0000\r
+\r
+On Sat, Nov 2, 2013 at 7:50 AM, Jani Nikula <jani@nikula.org> wrote:\r
+> On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:\r
+\r
+>> I think there should be a way to get the root mail of a thread,\r
+>> irrespective of the search order.\r
+>\r
+> Largely agreed. It's just that nobody's gotten around to doing this\r
+> yet. At the cli level I think the consensus is that the structured\r
+> (sexp/json) output format should contain multiple (or all) subjects.\r
+\r
+What about the default? (--format=text). What about user-interfaces\r
+that must display a summary of a thread?\r
+\r
+-- \r
+Felipe Contreras\r