On Wed, 29 Jun 2011 03:34:58 -0400, Austin Clements <amdragon@mit.edu> wrote: > Or, really, any file system, since notmuch doesn't currently take > advantage of sub-second mtimes. Oh, ouch. I hadn't realized that I'd codified the 1-second granularity mtime into the notmuch API. Oh well, we could extend that with a floating-point API as needed. > > Austin has a plan to fix the use of the mtime timestamp in notmuch, > > (never storing the current mtime in the database if it's the same as > > the current time), that should hopefully close this race window. > > Posted. Thanks! -Carl -- carl.d.worth@intel.com