unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Getting the right root mail of the thread
Date: Sun, 3 Nov 2013 14:12:52 -0600	[thread overview]
Message-ID: <CAMP44s2bdzgNb15bs7g8u1VECeqecQwTWXr+u4Ywj2z23qcsVw@mail.gmail.com> (raw)
In-Reply-To: <5276A289.3070605@fifthhorseman.net>

On Sun, Nov 3, 2013 at 1:22 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> On 11/02/2013 09:08 AM, Felipe Contreras wrote:
>>
>> Either way this doesn't make any sense to me. Each thread has a single
>> origin
>> mail, why would anybody would like to show a message other than that while
>> displaying the summary of the tread? Even more, why isn't there an option
>> to
>> fetch that information easily?
>
>
> It's entirely possible to make a message that has a References: header that
> includes message IDs from two different threads.

Right, there could be two or more roots. But we don't get either in
the summary, we can only get the first or the last one.

I say the summary should contain the earliest root, always. Or at
least have an option to get it.

-- 
Felipe Contreras

      reply	other threads:[~2013-11-03 20:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 13:08 Getting the right root mail of the thread Felipe Contreras
2013-11-02 13:50 ` Jani Nikula
2013-11-02 14:06   ` Felipe Contreras
2013-11-02 14:58     ` Jani Nikula
2013-11-03 20:10       ` Felipe Contreras
2013-11-03 20:17         ` Jani Nikula
2013-11-03 20:35   ` Jesse Rosenthal
2013-11-03 21:28     ` Jani Nikula
2013-11-03 21:44     ` Felipe Contreras
2013-11-03 19:22 ` Daniel Kahn Gillmor
2013-11-03 20:12   ` Felipe Contreras [this message]

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=CAMP44s2bdzgNb15bs7g8u1VECeqecQwTWXr+u4Ywj2z23qcsVw@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=dkg@fifthhorseman.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).