notmuch, branch 0.22.1

debian: changelog stanza for 0.22.1-1

2016-07-19T09:43:20Z

Basically copy upstream NEWS

NEWS: set date of point release

2016-07-19T09:36:15Z

version: bump to 0.22

2016-07-19T09:33:37Z

NEWS: initial NEWS for 0.22.1

2016-07-13T22:55:24Z

debian: add changelog stanza for 0.22.1~rc0-1

2016-06-30T19:28:31Z

No actual changes discussed, because the NEWS file is yet to be created.

version: bump to 0.21.1~rc0

2016-06-30T15:52:42Z

Getting ready for the point release

notmuch-mutt: use env to locate perl for increased portability

2016-06-30T15:50:16Z

Note: this patch drops -w from the shebang line, but we still have "use warnings" in the script, which is superior anyhow. Thanks Andreas Tolfsen for the suggestion.

lib: fix definition of LIBNOTMUCH_CHECK_VERSION

2016-06-30T15:49:29Z

Fix bug reported in id:20160606124522.g2y2eazhhrwjsa4h@flatcap.org Although the C99 standard 6.10 is a little non-obvious on this point, the docs for e.g. gcc are unambiguous. And indeed in practice with the extra space, this code fails #include #define foo (x) (x+1) int main(int argc, char **argv){ printf("%d\n",foo(1)); }

doc: forbid further operations on a closed database

2016-06-30T15:48:23Z

We could add many null pointer checks, but currently I don't see a use case that justifies it.

test: don't use dump and restore in a pipeline

2016-06-30T15:47:36Z

This has been wrong since bbbdf0478ea, but the race condition was not previously been (often?) triggered in the tests. With the DB_RETRY_LOCK patches, it manifests itself as a deadlock.