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 8968A6DE0AF8 for ; Sat, 13 Feb 2016 10:14:03 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.307 X-Spam-Level: X-Spam-Status: No, score=-0.307 tagged_above=-999 required=5 tests=[AWL=0.244, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001] 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 o2aZzqJPi3xV for ; Sat, 13 Feb 2016 10:14:01 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 7D76F6DE0A9A for ; Sat, 13 Feb 2016 10:14:01 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aUeh2-00054V-JL; Sat, 13 Feb 2016 13:13:16 -0500 Received: (nullmailer pid 22350 invoked by uid 1000); Sat, 13 Feb 2016 18:13:56 -0000 From: David Bremner To: Daniel Kahn Gillmor , Jameson Graef Rollins , Notmuch Mail Cc: Austin Clements Subject: Re: [PATCH v3 15/16] added notmuch_message_reindex In-Reply-To: <871t8ko50r.fsf@alice.fifthhorseman.net> References: <1454272801-23623-1-git-send-email-dkg@fifthhorseman.net> <1454272801-23623-16-git-send-email-dkg@fifthhorseman.net> <87mvr9s8gy.fsf@servo.finestructure.net> <87oabpnzt4.fsf@alice.fifthhorseman.net> <871t8ko50r.fsf@alice.fifthhorseman.net> User-Agent: Notmuch/0.21+26~g9404723 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sat, 13 Feb 2016 14:13:56 -0400 Message-ID: <87mvr47a1n.fsf@zancas.localnet> 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, 13 Feb 2016 18:14:03 -0000 Daniel Kahn Gillmor writes: > > I think when a message is removed from the database, we need to know > whether anything else (in its same thread?) refers to it. If so, we > should keep it around as a ghost message instead of fully removing it. > > does this sound like the right approach? > This seems right to me, but maybe Austin, in copy, can comment. d