notmuch, branch 0.23.3

NEWS: fix date and title

2016-11-27T01:54:10Z

NEWS: note disappearing files fix for notmuch new

2016-11-26T12:41:47Z

NEWS: set date

2016-11-26T12:39:32Z

debian: finalize? changelog for 0.23.3-1

2016-11-26T12:38:13Z

cli/new: document new exit code

2016-11-26T02:44:05Z

It seems important to give the numeric return code for people writing scripts. Hopefully deviations from this convention are rare.

cli: consider files vanishing during notmuch new non-fatal

2016-11-26T01:09:32Z

If some software other than notmuch new renames or removes files during the notmuch new scan (specifically after scandir but before indexing the file), keep going instead of bailing out. Failing to index the file is just a race condition between notmuch and the other software; the rename could happen after the notmuch new scan anyway. It's not fatal, and we'll catch the renamed files on the next scan. Add a new exit code for when files vanished, so the caller has a chance to detect the race and re-run notmuch new to recover. Reported by Paul Wise at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843127

debian: start changelog stanza for 0.23.3-1

2016-11-25T00:30:58Z

version: bump to 0.23.3

2016-11-25T00:29:18Z

NEWS: note gnupg related test-suite fix

2016-11-25T00:28:27Z

debian: disable dh_elpa_test

2016-11-25T00:25:35Z

Currently it seems to interfere with running the notmuch test suite. In any case we have no ert / buttercup format tests to run.