firstname.lastname@example.org writes: > Gaute Hope <email@example.com> writes: > Exactly. It could be a tick, or just the current time of day if your > clock does not go backwards. (I'd be willing to do a full scan if the > clock ever goes backwards.) The advantage of time is that you don't > have to synchronously update some counter. I think I'd lean towards global time so that one could use it to resolve conflicts between changes to multiple copies of the database. > Making sure the write-operations update the time should be easy. Most > or all of the changes are probably funneled through > _notmuch_message_sync. Worst case, there are only 9 places in the > source code that make use of a Xapian:WritableDatabase, so I'm pretty > confident total changes wouldn't be much more than 50 lines of code. Maybe. Don't forget upgrading the database, updating the test suite, and presumably some changes to the CLI so the new mtime can actually be used. Not to be discouraging ;). > I would do it myself if there were any kind of indication that such a > change could be upstreamed. I brought this up in January, 2011, and > didn't get a huge amount of interest in the ctime idea. But I was also > a lot less focused on what I needed. Now that I have a working > distributed setup and am actually using notmuch for my mail, I have a > much better understanding of what is needed. In the ensuing time, nothing better has developed for tag synchronization (my pet use case) so maybe it's time to pursue this again. It would be good to have some preliminary idea about the time and space costs of adding document mtimes. I guess database bloat should not be too bad, since it's only 64bits (?) per mail message.