thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.20 2015-03-15T19:27:20Z 2015-03-15T19:27:20Z David Bremner david@tethera.net 2015-03-14T07:32:22Z urn:sha1:baf93369f6a204bc16740358a56af95cbaa1f9b5 This is arguably testing the same thing twice, but in the brave new future where we don't use printf anymore, each subcommand will be responsible for handling the output on it's own. 2014-07-16T22:33:10Z Mark Walters markwalters1009@gmail.com 2014-06-23T20:12:29Z urn:sha1:bbbdf0478ea6109afc1ca5a26a8d1cd86b600e2a Dump currently only takes the read lock. Xapian can cope with some changes while maintaining a read snapshot but with more changes it fails. Currently notmuch just gives a xapian error. To avoid this we take the write lock when dumping. This prevents other notmuch processes from modifying the xapian database preventing this error. Discussion with Olly on irc indicates that this is currently the best solution: in xapian trunk there may be better possibilities using snapshots but they need to make it to a release and propogate out to users before we can switch approach. Finally, this breaks one use case: pipelines of the form notmuch dump | ... | notmuch restore According to Olly this is already very fragile: it will only work on small databases. One of the tests relies on this behaviour so fix that to store the dump rather than use a pipe. 2014-01-13T18:16:46Z Tomi Ollila tomi.ollila@iki.fi 2014-01-09T15:18:59Z urn:sha1:a755c9d6a9099366cc82ba3a4bee8e6d2b83d529 All test scripts to be executed are now named as T\d\d\d-name.sh, numers in increments of 10. This eases adding new tests and developers to see which are test scripts that are executed by test suite and in which order.