From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 63F83431FBC; Thu, 10 Dec 2009 10:16:36 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org 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 18abKxjFBGc1; Thu, 10 Dec 2009 10:16:35 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id BDB4A431FAE; Thu, 10 Dec 2009 10:16:35 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 0141F2542FF; Thu, 10 Dec 2009 09:39:54 -0800 (PST) From: Carl Worth To: Mark Anderson , notmuch In-Reply-To: <1260400470-sup-5775@testarossa> References: <1260400470-sup-5775@testarossa> Date: Thu, 10 Dec 2009 09:39:48 -0800 Message-ID: <87ws0ug23f.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Subject: Re: Threading X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 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: Thu, 10 Dec 2009 18:16:36 -0000 --=-=-= On Wed, 9 Dec 2009 16:21:34 -0700, Mark Anderson wrote: > I was wondering if there's a way in notmuch to group un-associated > threads into a single thread. There's certainly nothing like that in notmuch currently. Sup had user-level functionality in the interface for stitching messages into a single thread, and I definitely think that that doesn't make any sense. > I have a bug tracking system that doesn't give me emails that thread naturally in notmuch. I've seen similar things. Bugzilla emails at least all group into a single thread in notmuch, but don't get nested correctly at all, and that's really annoying. > I wouldn't mind writing a filter that could help identify a thread id > which should apply to a message, and suggest that to notmuch. I think the right answer here is to fix the input that notmuch is getting. Just ensure that each message has a proper In-Reply-To header and all should be fine. If you can't fix the bug-tracking system to emit proper email, can you apply your filter and rewrite the message as part of delivery (before notmuch sees it)? -Carl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLITJl6JDdNq8qSWgRAqjzAKCnCZsa7lTzORmfKbBrQmppkwXnDgCdHdtL 52r8Bi4++WdJfuG7UiP1NjQ= =vbuu -----END PGP SIGNATURE----- --=-=-=--