From dee18e5e8d133b9c28419daa277b5acb09b9c639 Mon Sep 17 00:00:00 2001 From: Tomi Ollila Date: Sun, 18 Sep 2016 18:15:09 +0300 Subject: [PATCH] cosmic --- news/release-0.19.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/news/release-0.19.mdwn b/news/release-0.19.mdwn index 0e70c6a..436763c 100644 --- a/news/release-0.19.mdwn +++ b/news/release-0.19.mdwn @@ -25,13 +25,13 @@ dump which would cause the dump to fail. Note, if another notmuch process already has the write lock the dump will not start, so script callers should still check the return value. -### `notmuch insert` requires succesful message indexing for success status +### `notmuch insert` requires successful message indexing for success status Previously the `notmuch insert` subcommand indicated success even if the message indexing failed, as long as the message was delivered to file system. This could have lead to delivered messages missing tags, etc. `notmuch insert` is now more strict, also requiring -succesful indexing for success status. Use the new `--keep` option +successful indexing for success status. Use the new `--keep` option to revert to the old behaviour (keeping the delivered message file and returning success even if indexing fails). @@ -161,7 +161,7 @@ from the config file. Use something like: ... }, ... - }, + } Python Bindings --------------- -- 2.43.0