--- /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 0E22B431FBF\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Apr 2014 04:54:29 -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 68tG4zIGmrQc for <notmuch@notmuchmail.org>;\r
+ Wed, 23 Apr 2014 04:54:22 -0700 (PDT)\r
+Received: from mail-la0-f41.google.com (mail-la0-f41.google.com\r
+ [209.85.215.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 3C76B431FBD\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Apr 2014 04:54:22 -0700 (PDT)\r
+Received: by mail-la0-f41.google.com with SMTP id gl10so679859lab.0\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Apr 2014 04:54:19 -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:content-type:from:to:cc:subject:in-reply-to\r
+ :references:date:message-id:user-agent:content-transfer-encoding;\r
+ bh=xtoOnRQWbi/IkmS+Wsi0ABHTYggeJzf+seFlJK7O6ng=;\r
+ b=MC5jgOzjbvmvDnzHvCfo9OBbz6+Z8Iv8BN1cy6ZAvnh7kDAzDdt/UYCEwEPZiG5KzD\r
+ Rc3qYwtQRaWInHi4fQkDFvkijqm5E0JTGrr7f7xr8U3PVA/6J5Yp/nicJ6yzGZ5BuqyB\r
+ sFdvrjr6gUWqCiEE6cH7Sf/k19Mk0NG8q8f3M86//id4LfrtVjVz4qzDYX8JllxAbxFL\r
+ fpdkTEprvpYilj280e1L9Myqpr97vNjHPwP5eZ1FbgCMiFa8TR+4ApMt0Y/NcngWjcQF\r
+ GfsuQQsOhP8qDsQU4azQs/DCJO9u/oGA91K/jwDMeMGhHllMAtpjaAuAyulI23yEC/7k\r
+ WQJA==\r
+X-Gm-Message-State:\r
+ ALoCoQlV45D3SXtic/4dGPC/kAC98UfArsn8ZqtPD8iLMwvizByz3qHAbw/r7gRFZgsPhT33ufL4\r
+X-Received: by 10.152.22.72 with SMTP id b8mr36745laf.63.1398254058245;\r
+ Wed, 23 Apr 2014 04:54:18 -0700 (PDT)\r
+Received: from localhost ([128.39.46.106])\r
+ by mx.google.com with ESMTPSA id u4sm730335laj.2.2014.04.23.04.54.16\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Wed, 23 Apr 2014 04:54:16 -0700 (PDT)\r
+Content-Type: text/plain; charset=UTF-8\r
+From: Gaute Hope <eg@gaute.vetsj.com>\r
+To: David Mazieres expires 2014-07-22 PDT\r
+ <mazieres-eqbxrjbqrn7vs5xdx45e9hkucs@temporary-address.scs.stanford.edu>\r
+Subject: Re: [PATCH] Add configurable changed tag to messages that have been\r
+ changed on disk\r
+In-reply-to: <87ioq0l8th.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> <1397163239-sup-5101@qwerzila>\r
+ <87d2g9ja0h.fsf@maritornes.cs.unb.ca> <1398237865-sup-624@qwerzila>\r
+ <87ioq0l8th.fsf@ta.scs.stanford.edu>\r
+Date: Wed, 23 Apr 2014 13:53:10 +0200\r
+Message-Id: <1398253735-sup-5203@qwerzila>\r
+User-Agent: Sup/git\r
+Content-Transfer-Encoding: 8bit\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, 23 Apr 2014 11:54:29 -0000\r
+\r
+Excerpts from David Mazieres's message of 2014-04-23 11:00:10 +0200:\r
+> Gaute Hope <eg@gaute.vetsj.com> writes:\r
+>\r
+> > A db-tick or a _good_ ctime solution can as far as I can see solve both\r
+> > David M's (correct me if I am wrong) and my purposes, as well as\r
+> > probably have more use cases in the future. It would even be an\r
+> > interesting direct search: show me everything that changed lately,\r
+> > sorted.\r
+>\r
+> I could live with a db-tick scheme. I would prefer a ctime scheme,\r
+> since then I can answer questions such as "what has changed in the last\r
+> five minutes"? I mean all kinds of other stuff starts to break if your\r
+> clock goes backwards on a mail server machine, not the least of which is\r
+> that incremental backups will fail silently, so you risk losing your\r
+> mail.\r
+>\r
+> A middle ground might be to use the maximum of two values: 1) the\r
+> time-of-day at which notmuch started executing, and 2) the highest ctime\r
+> in the database plus 100 microseconds (leaving plenty of slop to store\r
+> timestamps as IEEE doubles with 52 significant bits). Since the values\r
+> will be Btree-indexed, computing the max plus one will be cheap.\r
+>\r
+> Incidentally, if you are really this paranoid about time stamps, it\r
+> should bother you that notmuch's directory timestamps only have one\r
+> second granularity. It's not that hard to get a new message delivered\r
+> in the same second that notmuch new finished running. In my\r
+> synchronizer, I convert st_mtim (a struct timespec) into a double and\r
+> keep that plus size in the database to decide if I need to re-hash\r
+> files. But for directories, I'm stuck with NOTMUCH_VALUE_TIMESTAMP,\r
+> which are quantized to the second. (Ironically, I think\r
+> Xapian::sortable_serialize converts time_ts to doubles anyway, so\r
+> avoiding st_mtim is not really helping performance.)\r
+\r
+Agreed, it probably won't be the end of the world.. I will have to\r
+handle conflicts anyway. With an inclusion of ctime my 'changed'-tag\r
+patches are unnecessary.\r
+\r
+By the way, muchsync looks very promising!\r
+\r
+Cheers, gaute\r
+\r
projects / notmuch-archives.git / commitdiff