--- /dev/null
+Return-Path: <eg@gaute.vetsj.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 9F3D5431FBD\r
+ for <notmuch@notmuchmail.org>; Wed, 6 Aug 2014 02:02:15 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id oK675Mj8U+rj for <notmuch@notmuchmail.org>;\r
+ Wed, 6 Aug 2014 02:02:09 -0700 (PDT)\r
+Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com\r
+ [209.85.192.49]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 09051431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 6 Aug 2014 02:02:08 -0700 (PDT)\r
+Received: by mail-qg0-f49.google.com with SMTP id j107so2283507qga.36\r
+ for <notmuch@notmuchmail.org>; Wed, 06 Aug 2014 02:02:06 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:mime-version:in-reply-to:references:date\r
+ :message-id:subject:from:to:cc:content-type;\r
+ bh=EFNtoY+OKho8W9JL4obKen8R0ro//jQOXhbY8Gehqr8=;\r
+ b=Vae+bdvK1FhoRFc+fLVmoOa747UkpaxHY4A22noKCye/Ign2CBaOapvSXMde/w4dPR\r
+ /sXohlFJuq41bggd+tPs6yqizsYJIF4QMfEbVEnjT8MTAb4O2SkRuIprCIy25SKpg29r\r
+ QbK+l2Z7Pg7RLm/xEZp53rG+mdKMzMKtQGMmzvh8LF0R+2/abcW20LnNbrSgD/7tYzIN\r
+ iioZc5nZRP3z2iJJq8UliS5SRZ++rRgsdBYgZdYF7UnGnjHkWmUf04yi9mlzs9Ynddnz\r
+ VhgGSBqLJyRVds5I5+QDvkwYk4cXkQqPon5t8febClioc064JnVStc9x8RncGdTXIBUK\r
+ U/pg==\r
+X-Gm-Message-State:\r
+ ALoCoQkamNKklu4w5NNfkxtCKnEn9rg1OJJx8T0V0pBQXpgaaguX6PNkeqkrbae9Zcrj3LXz9tzS\r
+MIME-Version: 1.0\r
+X-Received: by 10.140.102.142 with SMTP id w14mr1218313qge.101.1407315726288; \r
+ Wed, 06 Aug 2014 02:02:06 -0700 (PDT)\r
+Received: by 10.140.86.148 with HTTP; Wed, 6 Aug 2014 02:02:06 -0700 (PDT)\r
+In-Reply-To: <20140801185505.GS13893@mit.edu>\r
+References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com>\r
+ <87fviiiuzn.fsf@maritornes.cs.unb.ca>\r
+ <CABKe4Mv6p77i5dBT9BV41hxmtrE4UPLR3NjZfpLuZDoE1KWYyA@mail.gmail.com>\r
+ <20140801185505.GS13893@mit.edu>\r
+Date: Wed, 6 Aug 2014 11:02:06 +0200\r
+Message-ID:\r
+ <CABKe4MskJk6JuJ29A8o1-U-5Sz-xUCTJXJqvq22PqodGQKRZdw@mail.gmail.com>\r
+Subject: Re: [PATCH] Add configurable changed tag to messages that have been\r
+ changed on disk\r
+From: Gaute Hope <eg@gaute.vetsj.com>\r
+To: Austin Clements <amdragon@mit.edu>\r
+Content-Type: text/plain; charset=UTF-8\r
+Cc: notmuch <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 06 Aug 2014 09:02:15 -0000\r
+\r
+On Fri, Aug 1, 2014 at 8:55 PM, Austin Clements <amdragon@mit.edu> wrote:\r
+> I have a prototype implementation of message modification times on my\r
+> lastmod-v1 branch at\r
+>\r
+> https://github.com/aclements/notmuch/tree/lastmod-v1\r
+>\r
+> It builds on my database features series that's currently awaiting\r
+> review [1].\r
+>\r
+> The series uses a monotonic revision number, rather than wall-clock\r
+> time, for reasons related to Xapian's concurrent control and detailed\r
+> in the main commit's commit message. The implementation isn't quite\r
+> useful from the CLI yet because I haven't added any way to query the\r
+> database's current revision number. (I'm still thinking about how I\r
+> want to do this, since search/show don't have a good way to deliver\r
+> "additional" information right now. I might just add the last\r
+> modification for each individual message/max of all messages in a\r
+> thread, similar to what Thomas Jost's patch did long ago.)\r
+>\r
+> [1] id:1406859003-11561-1-git-send-email-amdragon@mit.edu\r
+\r
+\r
+Hi,\r
+\r
+this should allow me to do what I wish to accomplish. The message\r
+deletion is still a problem though, I can see two options at the moment:\r
+\r
+a) output during notmuch new to a hook or a list somewhere deleted files.\r
+ if list: notmuch will not handle this list, only append to it and\r
+the user must\r
+ purge it when it is safe to do so.\r
+\r
+ if hook: for my purposes I would just create a hook appending to the\r
+ list. as a minimum I think thread_id, message_id and revision number\r
+ should be included.\r
+\r
+\r
+b) maintain a full list of deleted / dead messages. a user initiated\r
+ purge can clean this from the database. a tag could be used for this,\r
+ so that clients can ignore unlinked/deleted/dead messages. this\r
+ differs from a 'deleted' message (IMAP/Maildir context) that has not\r
+ yet been expunged so there is confusion to be avoided.\r
+\r
+ a garbage collection function and interface must also be set up, but\r
+ this one is probably simple.\r
+\r
+\r
+in most cases I think a) would be sufficient, and probably much easier\r
+to do. it might be slow in cases where large amounts of messages have been\r
+deleted, but this is seldom the case for me at least.\r
+\r
+cheers, gaute\r