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 BEF1440D166 for ; Fri, 29 Oct 2010 13:23:28 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham 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 ULfSpr5utNqb; Fri, 29 Oct 2010 13:23:18 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 800D840D164; Fri, 29 Oct 2010 13:23:18 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 278F92540F4; Fri, 29 Oct 2010 13:23:18 -0700 (PDT) From: Carl Worth To: Arvid Picciani , notmuch@notmuchmail.org Subject: Re: Fix missing References from broken muas. In-Reply-To: <87pr16efjp.fsf@exys.org> References: <87pr16efjp.fsf@exys.org> User-Agent: Notmuch/0.3.1-137-gce6390c (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Fri, 29 Oct 2010 13:23:17 -0700 Message-ID: <87vd4k6956.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: Fri, 29 Oct 2010 20:23:28 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Sat, 08 May 2010 14:36:26 +0200, Arvid Picciani wrote: > Most of my mail comes from the 50MLs i'm subscribed to. Unfortunately > some MUAs suck that much, they don't even respond in threads. > My idea how to fix them would be: People have previously asked for a feature to combine messages into the same thread. And it would actually be a fairly simple operation. Perhaps it could be something like: notmuch set-thread $(notmuch search --threads ) The bigger problem is that as soon as we have an operation to join threads, people are going to need an operation to split threads. (And some people want this already for cases where people reply when they should have composed a new message.) The split case is harder in that it will require some extra stashing of information about the intent of the split, (otherwise, the current logic will recombine things when a future message arrives that References: messages from two split threads). So I think we'd need a proposal to handle that before we could do splitting. The proposal I'm looking for here would be at the database level, not the command-line level. =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMyy016JDdNq8qSWgRAgGjAJ9gADD5o07r+GNAitv11mUaMXR7VQCdEMXS HEAnRYpmN+OQG2awj9w/rGY= =yi8F -----END PGP SIGNATURE----- --=-=-=--