From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 4DF8E6DE022D for ; Mon, 23 Jul 2018 01:41:59 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7UEcIjukiUe for ; Mon, 23 Jul 2018 01:41:58 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 806076DE022A for ; Mon, 23 Jul 2018 01:41:58 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1fhWPk-0005cG-MA; Mon, 23 Jul 2018 04:41:56 -0400 Received: (nullmailer pid 3085 invoked by uid 1000); Mon, 23 Jul 2018 08:41:51 -0000 From: David Bremner To: Gregor Zattler , notmuch@notmuchmail.org Subject: Re: v1: fix for threading of replies to ghost messages In-Reply-To: <871sbwbifq.fsf@len.workgroup> References: <20180720233746.2844-1-david@tethera.net> <871sbwbifq.fsf@len.workgroup> Date: Mon, 23 Jul 2018 16:41:51 +0800 Message-ID: <87zhyigx80.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 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: Mon, 23 Jul 2018 08:41:59 -0000 Gregor Zattler writes: > > I applied the patches and looked with notmuch-emacs for threads > which before would probably show wrong ordering of messages. The > half a dozen threads were all shown in the correct order with > respect to parents and children, but I found from those not > disclosable RT ticket mails (I mentioned in above referenced > thread): Can you also try the series at id:20180723082259.32440-1-david@tethera.net? I'm not sure if it's related, but it does fix replies for a different bug tracker. You will have to reindex the messages in question (e.g. using notmuch reindex).