Re: notmuch-lazysync -- synchronizing tags using dropbox

diff --git a/1c/cebe1d4c6735f74726053af71e2e2ed99d5db9 b/1c/cebe1d4c6735f74726053af71e2e2ed99d5db9
new file mode 100644 (file)
index 0000000..8f21119
--- /dev/null
+++ b/1c/cebe1d4c6735f74726053af71e2e2ed99d5db9
@@ -0,0 +1,79 @@
+Return-Path:\r
+ <return-e6de6hhfxhg7pvcfnevedheczw@temporary-address.scs.stanford.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 21B066DE0AD1\r
+ for <notmuch@notmuchmail.org>; Tue, 21 Jul 2015 17:41:46 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.067\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.067 tagged_above=-999 required=5 tests=[AWL=0.784,\r
+  RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id XpgmEdX6ooXQ for <notmuch@notmuchmail.org>;\r
+ Tue, 21 Jul 2015 17:41:43 -0700 (PDT)\r
+X-Greylist: delayed 1534 seconds by postgrey-1.35 at arlo;\r
+ Tue, 21 Jul 2015 17:41:43 PDT\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 7928E6DE0A87\r
+ for <notmuch@notmuchmail.org>; Tue, 21 Jul 2015 17:41:43 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ t6M0G7id010666; Tue, 21 Jul 2015 17:16:07 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t6M0G6Fj030472;\r
+ Tue, 21 Jul 2015 17:16:06 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-e6de6hhfxhg7pvcfnevedheczw@ta.scs.stanford.edu using -f\r
+From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>\r
+To: Daniel Schoepe <daniel@schoepe.org>, notmuch@notmuchmail.org\r
+Subject: Re: notmuch-lazysync -- synchronizing tags using dropbox\r
+In-Reply-To: <87a8upjqts.fsf@schoepe.localhost>\r
+References: <87a8upjqts.fsf@schoepe.localhost>\r
+Reply-To: David Mazieres expires 2015-10-19 PDT\r
+ <mazieres-cveh8aunzppx7vn8bfg87dyijs@temporary-address.scs.stanford.edu>\r
+Date: Tue, 21 Jul 2015 17:16:05 -0700\r
+Message-ID: <871tg1yrlm.fsf@ta.scs.stanford.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.18\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, 22 Jul 2015 00:41:46 -0000\r
+\r
+Daniel Schoepe <daniel@schoepe.org> writes:\r
+\r
+> The way tag changes are logged is a bit of a hack, but it could be\r
+> improved in the future by adding a post-tag hook to notmuch.\r
+\r
+One thing to look into, if you are thinking of a better logging\r
+mechanism, is that Xapian itself has a change logging mechanism for\r
+replicating databases (http://xapian.org/docs/replication.html).\r
+\r
+I do think it would be cleaner to do this in a way that is integrated\r
+with notmuch, but I think the best way to do this is to integrate a\r
+"modtime" value into the Xapian database.  Having a modtime for each\r
+record would not only allow incremental transfers (just record the\r
+highest timestamp sent to each replica), it would also solve this\r
+terrible problem that in emacs you can end up tagging messages you don't\r
+see (because you apply a tag to the query result, when new mail has come\r
+in--which would be solved by tagging only through the higest modtime\r
+actually displayed).\r
+\r
+When you have one mechanism (modtime) that solves multiple problems, it\r
+is likely the right thing to use...\r
+\r
+David\r