From bb0ba110b20127035e2fbab2e580b2b5e2dbdd7c Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Wed, 13 Feb 2013 11:17:08 +1600 Subject: [PATCH] RE: Reply all - issue --- cd/0aba0966eabe604018956a9f1b8db8848226fe | 111 ++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 cd/0aba0966eabe604018956a9f1b8db8848226fe diff --git a/cd/0aba0966eabe604018956a9f1b8db8848226fe b/cd/0aba0966eabe604018956a9f1b8db8848226fe new file mode 100644 index 000000000..3dafa6f65 --- /dev/null +++ b/cd/0aba0966eabe604018956a9f1b8db8848226fe @@ -0,0 +1,111 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 93B6A431FB6 + for ; Tue, 12 Feb 2013 11:14:32 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0 +X-Spam-Level: +X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] + autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id 6yAEgKhSGjB5 for ; + Tue, 12 Feb 2013 11:14:32 -0800 (PST) +Received: from arlo.cworth.org (arlo.cworth.org [50.126.95.6]) + (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 09EA2431FAF + for ; Tue, 12 Feb 2013 11:14:32 -0800 (PST) +Received: from yoom.home.cworth.org (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id 0D0BE6DE0941; + Tue, 12 Feb 2013 11:14:30 -0800 (PST) +Received: by yoom.home.cworth.org (Postfix, from userid 1000) + id 44C3E64933; Wed, 13 Feb 2013 06:17:18 +1100 (EST) +From: Carl Worth +To: Jameson Graef Rollins , + David Bremner , + Robert Mast , + 'Jani Nikula' , notmuch@notmuchmail.org +Subject: RE: Reply all - issue +In-Reply-To: <87sj52nh6h.fsf@servo.finestructure.net> +References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org> + <002601cdfd83$83b283f0$8b178bd0$@nl> + <87boc8bt8a.fsf@yoom.home.cworth.org> + <000001cdff33$afe11070$0fa33150$@nl> + <87txpykve8.fsf@zancas.localnet> <87r4l2kvak.fsf@zancas.localnet> + <87sj52nh6h.fsf@servo.finestructure.net> +User-Agent: Notmuch/0.13.1 (http://notmuchmail.org) Emacs/23.4.1 + (x86_64-pc-linux-gnu) +Date: Tue, 12 Feb 2013 11:17:08 -0800 +Message-ID: <877gmdjqa3.fsf@yoom.home.cworth.org> +MIME-Version: 1.0 +Content-Type: multipart/signed; boundary="=-=-="; + micalg=pgp-sha1; protocol="application/pgp-signature" +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Tue, 12 Feb 2013 19:14:32 -0000 + +--=-=-= +Content-Type: text/plain; charset=utf-8 +Content-Transfer-Encoding: quoted-printable + +Jameson Graef Rollins writes: +> Just a thought: what if messages with a given tag (e.g. "new-thread") +> were always treated as the source of a new thread? + +It's a good start. And an approach like that would have the advantage +that one could undo a thread-split by just removing the tag. (That's not +an explicit thread-join feature, but I don't think anyone has ever asked +for that.) + +> A message with the given tag could just be (re)indexed with any +> In-Reply-To/References headers stripped before indexing. + +It would require a little more than that. Imagine this thread: + + A: Subject: An original thread + =E2=94=94=E2=94=80B: Subject: Thread hijacking is fun (tag:new-thread) + =E2=94=94=E2=94=80C: Subject: Re: Thread hijacking is fun + +In this case, message C is likely to have a References header that +mentions both A and B. So the thread stitching logic in notmuch will +want to merge threads A and B when indexing C. So special care will have +to be taken here as well, (not just when indexing B). + +And that special care may not be cheap if it requires additional +database lookups for each unique thread ID encountered among references +of a message. + +Though, I don't mean to dissuade anyone from thinking this through and +coding it up. The relevant code for the pieces I'm referring to starts +in _notmuch_database_link_message in lib/database.cc. + +=2DCarl + +=2D-=20 +carl.d.worth@intel.com + +--=-=-= +Content-Type: application/pgp-signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlEalTQACgkQ6JDdNq8qSWguyQCfbtLt8QIx19Mjhbb7q/5BuEJe +z5sAniG0T+bewnGDgmcAd+IUAQOJpD7Z +=su3/ +-----END PGP SIGNATURE----- +--=-=-=-- -- 2.26.2