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 A2C016DE091E for ; Thu, 30 Aug 2018 05:52:25 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[AWL=0.013, 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 wH4Q3kLCKJG3 for ; Thu, 30 Aug 2018 05:52:24 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 5A57E6DE0361 for ; Thu, 30 Aug 2018 05:52:24 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1fvMQw-0007cx-7v; Thu, 30 Aug 2018 08:52:22 -0400 Received: (nullmailer pid 26579 invoked by uid 1000); Thu, 30 Aug 2018 12:52:20 -0000 From: David Bremner To: "Naveen N. Rao" , notmuch@notmuchmail.org Subject: Re: 'notmuch search thread:<>' lists multiple threads In-Reply-To: <87zhzccrwg.fsf@tethera.net> References: <1523007700.l8xm6nm6af.naveen@linux.ibm.com> <87sh86v1oc.fsf@tethera.net> <878t9wvbmu.fsf@tethera.net> <1524045467.a0aq8zermb.naveen@linux.ibm.com> <87r2n8m5ky.fsf@tethera.net> <1530181883.fliclpetue.naveen@linux.ibm.com> <87zhzccrwg.fsf@tethera.net> Date: Thu, 30 Aug 2018 09:52:20 -0300 Message-ID: <87d0u0nhiz.fsf@unb.ca> 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: Thu, 30 Aug 2018 12:52:25 -0000 David Bremner writes: > "Naveen N. Rao" writes: > >> >> Were you able to look into this again? >> Using a list of in-reply-to values sounds like a good option, though I >> clearly have no idea about other consequences from that. If you have a >> patch, I can help test that. >> > > Sorry I haven't made any progress on this. Thanks for the reminder. > > d It's not much progress but I did manage to make a test case. id:20180730224555.26047-16-david@tethera.net As it says in the commit message, its not 100% clear this is your problem, but it is a bug, and hopefully fixing it will help your issue. d