[PATCH 4/4] Update NEWS for user.other_name
[notmuch-archives.git] / 6d / d224c7d08f9440bece44247ec7ba4f26c4558d
1 Return-Path: <felipe.contreras@gmail.com>\r
2 X-Original-To: notmuch@notmuchmail.org\r
3 Delivered-To: notmuch@notmuchmail.org\r
4 Received: from localhost (localhost [127.0.0.1])\r
5         by olra.theworths.org (Postfix) with ESMTP id 4B96D431FD0\r
6         for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 07:13:09 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.799\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
13         FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
14 Received: from olra.theworths.org ([127.0.0.1])\r
15         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
16         with ESMTP id 9d2oBC3IFtj4 for <notmuch@notmuchmail.org>;\r
17         Sat,  2 Nov 2013 07:13:04 -0700 (PDT)\r
18 Received: from mail-la0-f42.google.com (mail-la0-f42.google.com\r
19         [209.85.215.42]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
20         (No client certificate requested)\r
21         by olra.theworths.org (Postfix) with ESMTPS id 93C5C431FC3\r
22         for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 07:13:04 -0700 (PDT)\r
23 Received: by mail-la0-f42.google.com with SMTP id ea20so4238283lab.15\r
24         for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 07:13:01 -0700 (PDT)\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
26         h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
27         :cc:content-type;\r
28         bh=R4pA1gj+BPkoPnNIl4RfrlJZrWbUvd79x6AfEc8Jirk=;\r
29         b=z3Ga6aRcItd770XIcYuUK9MWG05DrTPbCs/njzIHe+OmfAz4Jp/AuoF+bTJGUjBdXP\r
30         nwuny5SotmkO6AgCkVkMt47f+QGeW4bIB7BCzMGL2GnepoeTzh5t8Cd8CvMEO07IRoKo\r
31         z0zQaku+mp+rraueBWMJqYwqCBtDkpFJk7+lYZF3FaOy3fIg8KIxFLAgjs9ECWDyvHoT\r
32         UujgCpb+coYg0rCUKfDpWXjFk5Y4janSpxXC5XepSgVjlg5Xjy4SOQt3prJOZe8iUT6z\r
33         r+mqUeaDh9LKJdypAhvjMggNGDg2lKT0GkB8di7H23koGeyFZpG/eQluHCx5rv8wNmwZ\r
34         aBog==\r
35 MIME-Version: 1.0\r
36 X-Received: by 10.152.45.42 with SMTP id j10mr5067931lam.15.1383401183622;\r
37         Sat, 02 Nov 2013 07:06:23 -0700 (PDT)\r
38 Received: by 10.114.201.69 with HTTP; Sat, 2 Nov 2013 07:06:23 -0700 (PDT)\r
39 In-Reply-To: <87zjpmoqtz.fsf@nikula.org>\r
40 References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
41         <87zjpmoqtz.fsf@nikula.org>\r
42 Date: Sat, 2 Nov 2013 08:06:23 -0600\r
43 Message-ID:\r
44  <CAMP44s19GP0w9UTTzeos2wQXHuYLpfF74BdJpxvLy=RD16=HXg@mail.gmail.com>\r
45 Subject: Re: Getting the right root mail of the thread\r
46 From: Felipe Contreras <felipe.contreras@gmail.com>\r
47 To: Jani Nikula <jani@nikula.org>\r
48 Content-Type: text/plain; charset=UTF-8\r
49 Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>\r
50 X-BeenThere: notmuch@notmuchmail.org\r
51 X-Mailman-Version: 2.1.13\r
52 Precedence: list\r
53 List-Id: "Use and development of the notmuch mail system."\r
54         <notmuch.notmuchmail.org>\r
55 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
56         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
57 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
58 List-Post: <mailto:notmuch@notmuchmail.org>\r
59 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
60 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
61         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
62 X-List-Received-Date: Sat, 02 Nov 2013 14:13:09 -0000\r
63 \r
64 On Sat, Nov 2, 2013 at 7:50 AM, Jani Nikula <jani@nikula.org> wrote:\r
65 > On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:\r
66 \r
67 >> I think there should be a way to get the root mail of a thread,\r
68 >> irrespective of the search order.\r
69 >\r
70 > Largely agreed. It's just that nobody's gotten around to doing this\r
71 > yet. At the cli level I think the consensus is that the structured\r
72 > (sexp/json) output format should contain multiple (or all) subjects.\r
73 \r
74 What about the default? (--format=text). What about user-interfaces\r
75 that must display a summary of a thread?\r
76 \r
77 -- \r
78 Felipe Contreras\r