--- /dev/null
+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 203DF429E3E\r
+ for <notmuch@notmuchmail.org>; Sun, 3 Nov 2013 12:10:46 -0800 (PST)\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 XnGLvWltl+Ve for <notmuch@notmuchmail.org>;\r
+ Sun, 3 Nov 2013 12:10:38 -0800 (PST)\r
+Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com\r
+ [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 4F7F7429E38\r
+ for <notmuch@notmuchmail.org>; Sun, 3 Nov 2013 12:10:38 -0800 (PST)\r
+Received: by mail-lb0-f181.google.com with SMTP id x18so4793635lbi.40\r
+ for <notmuch@notmuchmail.org>; Sun, 03 Nov 2013 12:10:36 -0800 (PST)\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=NgtdF29Eg4XM6ylby9bZZm3VWFYJfPGbU31VD03U11Y=;\r
+ b=rItyyX8ThBS5O/WpPPD7rDHXmfsBk5hJcZ8/g603D46UyoCMEPlDoIMlnNneS4svbf\r
+ 0heUSPmJF/3Cz3FegWzxvpbCrbWKxfvtq3NjBecrA82CXD5XzSHufm2yjAUmn3Jaa5d/\r
+ cs1Z70Ov8p4jCkZ72fcdmYeGcblZFv3tvFU4lvqQojZDlofR8rQriK3Y+g4O+KwrtzQh\r
+ T2jcip+tktMKMHS4pgctbGcXOhbI0QfLDD4pCuwqSFrTEwZJBWkAh/vEmmcIK44ToMNZ\r
+ 4EohZjPuS5xihnwRELOZdMntAdFfTlyESxu8WCkY3L5w4UfO82/VYw0c7Ur04yQzRU8w\r
+ FkFg==\r
+MIME-Version: 1.0\r
+X-Received: by 10.112.29.147 with SMTP id k19mr8955295lbh.9.1383509434106;\r
+ Sun, 03 Nov 2013 12:10:34 -0800 (PST)\r
+Received: by 10.114.201.69 with HTTP; Sun, 3 Nov 2013 12:10:33 -0800 (PST)\r
+In-Reply-To: <87wqkqono3.fsf@nikula.org>\r
+References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
+ <87zjpmoqtz.fsf@nikula.org>\r
+ <CAMP44s19GP0w9UTTzeos2wQXHuYLpfF74BdJpxvLy=RD16=HXg@mail.gmail.com>\r
+ <87wqkqono3.fsf@nikula.org>\r
+Date: Sun, 3 Nov 2013 14:10:33 -0600\r
+Message-ID:\r
+ <CAMP44s1aCWBFX1WdgTLZVcgKRdWLyi-npJqTcWeGHj+BrTpOWQ@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: Sun, 03 Nov 2013 20:10:46 -0000\r
+\r
+On Sat, Nov 2, 2013 at 8:58 AM, Jani Nikula <jani@nikula.org> wrote:\r
+> On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:\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
+> To be honest, we haven't had much interest in adding new content or\r
+> features to the text output formats. It's just much easier to do this in\r
+> a backwards compatible way in the structured output formats, for which\r
+> we also have the format versioning. The emacs ui uses the sexp format\r
+> for the thread summaries.\r
+\r
+How is this any better?\r
+\r
+(:thread "000000000000826a" :timestamp 1383396519 :date_relative\r
+"Yest. 06:48" :matched 45 :total 45 :authors "Felipe Contreras"\r
+:subject "[PATCH/TEST 44/44] request-pull: rewrite to C" :tags ("sent"\r
+"to-me"))\r
+\r
+-- \r
+Felipe Contreras\r