unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Robert Mast" <beheerder@tekenbeetziekten.nl>
To: "'Jani Nikula'" <jani@nikula.org>, <notmuch@notmuchmail.org>
Subject: RE: Reply all - issue
Date: Mon, 28 Jan 2013 19:15:55 +0100	[thread overview]
Message-ID: <002601cdfd83$83b283f0$8b178bd0$@nl> (raw)
In-Reply-To: <87wquxjq7k.fsf@nikula.org>

Thanks for your reply.

I never tried gmail-conversation threading, but from your first reference I
understand it breaks threads on subject unconditionally.

Breaking on subject unconditionally would be even easier to implement, as
comparing the contents of previous messages takes performance and as long as
the crucial linking messages aren't read the outcome is ambiguous and would
lead to the annoying jumping of results.

I'll watch for 'client-end' solutions, but the mail that broke all those
mailers originated from my own mailprogram, I think Outlook 2010, so
automatic clearing references and in-reply-to when the user clears the
subject and body isn't common practice for MUA's.

Your point on patch-breaking related to gmail and my proposal isn't
completely clear to me, but I've probably addressed it well with my new
approach.

I'll study the code for adding the option of unconditional (stripped)
subject breaking on top of the existing thread-breaking.

  reply	other threads:[~2013-01-28 18:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 21:58 Reply all - issue Robert Mast
2013-01-28 15:13 ` Jani Nikula
2013-01-28 18:15   ` Robert Mast [this message]
2013-01-29  2:47     ` Carl Worth
2013-01-30 17:14       ` Robert Mast
2013-01-30 21:39         ` Suvayu Ali
2013-01-31 10:21           ` Andrei POPESCU
2013-01-30 20:56       ` Robert Mast
2013-01-30 21:49       ` Robert Mast
2013-01-31  1:12         ` David Bremner
2013-01-31  1:14           ` David Bremner
2013-02-12  7:07             ` Jameson Graef Rollins
2013-02-12 19:17               ` Carl Worth
2013-01-31 10:52 ` Michał Nazarewicz
2013-02-02 16:21   ` Robert Mast
2013-02-02 20:52     ` David Bremner
2013-02-03  0:06       ` [Spam-verdenking][english 100%] " Robert Mast
2013-02-03 15:26       ` Robert Mast
2013-02-03 18:28         ` David Bremner
2013-02-10 15:43       ` Robert Mast
2013-02-04 10:39     ` Michał Nazarewicz
2013-02-04 15:29       ` Suvayu Ali
2013-02-06 18:19       ` Istvan Marko

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='002601cdfd83$83b283f0$8b178bd0$@nl' \
    --to=beheerder@tekenbeetziekten.nl \
    --cc=jani@nikula.org \
    --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).