Re: [PATCH] Add configurable changed tag to messages that have been changed on disk

diff --git a/47/51277ef23b7cd84fc326a304a7f018b9f5e6b8 b/47/51277ef23b7cd84fc326a304a7f018b9f5e6b8
new file mode 100644 (file)
index 0000000..6aa317a
--- /dev/null
+++ b/47/51277ef23b7cd84fc326a304a7f018b9f5e6b8
@@ -0,0 +1,91 @@
+Return-Path: <david@tethera.net>\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 1DE9A431FAF\r
+       for <notmuch@notmuchmail.org>; Fri, 11 Apr 2014 04:09:04 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 ZjtPbJ1G8cVB for <notmuch@notmuchmail.org>;\r
+       Fri, 11 Apr 2014 04:08:58 -0700 (PDT)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 2CFA4431FAE\r
+       for <notmuch@notmuchmail.org>; Fri, 11 Apr 2014 04:08:58 -0700 (PDT)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+       (envelope-from <david@tethera.net>)\r
+       id 1WYZKE-0004WO-4E; Fri, 11 Apr 2014 08:08:50 -0300\r
+Received: (nullmailer pid 6460 invoked by uid 1000); Fri, 11 Apr 2014\r
+       11:08:46 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: David Mazieres expires 2014-07-09 PDT\r
+       <mazieres-gzp7rfravpipmg73ew8cs6n6t6@temporary-address.scs.stanford.edu>,\r
+       Gaute Hope <eg@gaute.vetsj.com>\r
+Subject: Re: [PATCH] Add configurable changed tag to messages that have been\r
+       changed on disk\r
+In-Reply-To: <87wqexnqvb.fsf@ta.scs.stanford.edu>\r
+References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com>\r
+       <87wqf2gqig.fsf@ta.scs.stanford.edu> <1397140962-sup-6514@qwerzila>\r
+       <87wqexnqvb.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.17+180~g8977b1a (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Fri, 11 Apr 2014 08:08:46 -0300\r
+Message-ID: <87k3aw5dj5.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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: Fri, 11 Apr 2014 11:09:04 -0000\r
+\r
+dm-list-email-notmuch@scs.stanford.edu writes:\r
+\r
+> Gaute Hope <eg@gaute.vetsj.com> writes:\r
+\r
+> Exactly.  It could be a tick, or just the current time of day if your\r
+> clock does not go backwards.  (I'd be willing to do a full scan if the\r
+> clock ever goes backwards.)  The advantage of time is that you don't\r
+> have to synchronously update some counter.\r
+\r
+I think I'd lean towards global time so that one could use it to resolve\r
+conflicts between changes to multiple copies of the database.\r
+\r
+> Making sure the write-operations update the time should be easy.  Most\r
+> or all of the changes are probably funneled through\r
+> _notmuch_message_sync.  Worst case, there are only 9 places in the\r
+> source code that make use of a Xapian:WritableDatabase, so I'm pretty\r
+> confident total changes wouldn't be much more than 50 lines of code.\r
+\r
+Maybe. Don't forget upgrading the database, updating the test suite, and\r
+presumably some changes to the CLI so the new mtime can actually be\r
+used. Not to be discouraging ;).\r
+\r
+> I would do it myself if there were any kind of indication that such a\r
+> change could be upstreamed.  I brought this up in January, 2011, and\r
+> didn't get a huge amount of interest in the ctime idea.  But I was also\r
+> a lot less focused on what I needed.  Now that I have a working\r
+> distributed setup and am actually using notmuch for my mail, I have a\r
+> much better understanding of what is needed.\r
+\r
+In the ensuing time, nothing better has developed for tag\r
+synchronization (my pet use case) so maybe it's time to pursue this\r
+again.  It would be good to have some preliminary idea about the time\r
+and space costs of adding document mtimes.  I guess database bloat\r
+should not be too bad, since it's only 64bits (?) per mail message.\r