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 165B76DE00DF for ; Sat, 6 Aug 2016 16:51:12 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.008 X-Spam-Level: X-Spam-Status: No, score=-0.008 tagged_above=-999 required=5 tests=[AWL=0.003, 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 9AwDjIvmL6MY for ; Sat, 6 Aug 2016 16:51:03 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 945936DE00C9 for ; Sat, 6 Aug 2016 16:51:03 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1bWBN5-0005rh-Fy; Sat, 06 Aug 2016 19:51:15 -0400 Received: (nullmailer pid 28572 invoked by uid 1000); Sat, 06 Aug 2016 23:50:54 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: thread merge/split proposal In-Reply-To: <87d1pvsjfx.fsf@alice.fifthhorseman.net> References: <87mvp9uwi4.fsf@alice.fifthhorseman.net> <87k2kdutao.fsf@alice.fifthhorseman.net> <878u0l8uyv.fsf@zancas.localnet> <87egabu5ta.fsf@alice.fifthhorseman.net> <8737qr7ig6.fsf@zancas.localnet> <87d1pvsjfx.fsf@alice.fifthhorseman.net> User-Agent: Notmuch/0.22.1+61~g2ce0f13 (https://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sun, 07 Aug 2016 08:50:54 +0900 Message-ID: <878tw98nj5.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Sat, 06 Aug 2016 23:51:12 -0000 Daniel Kahn Gillmor writes: > That still doesn't cover the "notmuch unjoin" semantics i'd sketched out > earlier, though. that might need to be a different use case. > > The semantics would be something like: > > break the selected threads into threads based solely on their > References headers (including any manual reference terms) using > connected component analysis, restoring the threading to what would be > produced on a clean import. One thing I haven't understood is if the problem this is working around is unavoidable due to the order messages arrive (or some other factor) or if this is just a workaround for bugs in the threading algorithm. I'm guessing the former, but can you explain why the problem is intractable enough that the right answer is to reindex a thread (btw, that might be a UI, to use the reindex command introduced in your indexed plaintex patches). d