diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2016-09-12 04:23:48 +0200 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2016-09-12 08:16:35 -0300 |
| commit | 89c8d279480aa618bed5ef074f9166dbf818e6eb (patch) | |
| tree | 593d8ebb2d669c02e9810b9618c04955fa454098 /NEWS | |
| parent | d25d33ff2d818d5a423e07b7f465add9c970dc75 (diff) | |
clean up spelling
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -483,13 +483,13 @@ Stopped `notmuch dump` failing if someone writes to the database 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). |