thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.18_rc1 2014-04-17T22:53:57Z 2014-04-17T22:53:57Z David Bremner david@tethera.net 2014-04-13T12:42:49Z urn:sha1:320f86c30a51017c2afd1b5ac02aaf2cb0affcd7 - The old test was quite impossible to debug; the new one shows the difference between the two directories, if any. - "repository" doesn't make sense for out of tree builds. Or tarball builds, for that matter. 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-04-02T00:34:52Z urn:sha1:b8327ab483a3f018b9c7c72502f2b30f8a80ccbe 'pre upgrade dump' is not much of a test, but at least this way we get somewhat sensible behaviour if it fails. 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-04-01T14:06:05Z urn:sha1:a7eaa4d84a909275fe0c089f8dbf346ebcdc69c6 All we do here is calculate the backup filename, and call the existing dump routine. Also take the opportunity to add a message about being safe to interrupt. 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-03-29T18:12:28Z urn:sha1:4c62d9366a389b7ddca796009d1dfe6a885cfde0 We rely completely on zlib to do the right thing in detecting gzipped input. Since our dump format is chosen to be 7 bit ascii, this should be fine. 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-04-03T11:02:23Z urn:sha1:de71c4d734bda72eb54b2874935dbd948610ddbe Recent proposed patches for gzipped input had a bug with handling missing newlines that was not caught by the current test suite 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-03-29T01:14:51Z urn:sha1:3c13bc0321baaf340663779d6fce2b1f34c1c2c3 The main goal is to support gzipped output for future internal calls (e.g. from notmuch-new) to notmuch_database_dump. The additional dependency is not very heavy since xapian already pulls in zlib. We want the dump to be "atomic", in the sense that after running the dump file is either present and complete, or not present. This avoids certain classes of mishaps involving overwriting a good backup with a bad or partial one. 2014-04-05T15:52:42Z Jani Nikula jani@nikula.org 2014-03-30T21:21:48Z urn:sha1:6812136bf576d894591606d9e10096719054d1f9 We've supported mbox files containing a single message for historical reasons, but the support has been deprecated, with a warning message while indexing, since Notmuch 0.15. Finally drop the support, and consider all mbox files non-email. 2014-03-26T10:43:36Z Jani Nikula jani@nikula.org 2014-03-26T08:48:12Z urn:sha1:d7d728a6220e490eae2445fd3b6afec470c8cf6a If neither sphinx nor rst2man is available, the notmuch man pages will not be available. Take this into account in the help system test. 2014-03-25T22:57:06Z Austin Clements amdragon@MIT.EDU 2014-03-11T22:19:54Z urn:sha1:92c3fd938e7a4e86edbc872eb5348dc048ec0e78 Previously, the term escaper used a blacklist of characters that needed escaping. This blacklist turned out to be somewhat incomplete; for example, it did not contain non-whitespace ASCII control characters or Unicode "fancy quotes", both of which do require the term to be escaped. Switch to a whitelist of characters that are definitely safe to leave unquoted. This fixes the broken test introduced by the previous patch. 2014-03-25T22:50:47Z Austin Clements amdragon@MIT.EDU 2014-03-11T22:19:53Z urn:sha1:716af7deb8d0692ec3c867a599e29da61027b808 The current term escaper gets most of these right, but fails to escape things containing Unicode "fancy quotes" or things containing non-whitespace control characters.