debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-11-22 10:58:10 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

clean up spelling

Browse source
This commit is contained in:
Daniel Kahn Gillmor 2016-09-12 04:23:48 +02:00 committed by David Bremner
parent d25d33ff2d
commit 89c8d27948
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
NEWS
View file

@ -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 process already has the write lock the dump will not start, so
script callers should still check the return value. 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 Previously the `notmuch insert` subcommand indicated success even if
the message indexing failed, as long as the message was delivered to the message indexing failed, as long as the message was delivered to
file system. This could have lead to delivered messages missing file system. This could have lead to delivered messages missing
tags, etc. `notmuch insert` is now more strict, also requiring 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 to revert to the old behaviour (keeping the delivered message file
and returning success even if indexing fails). and returning success even if indexing fails).

2
doc/man1/notmuch-dump.rst
View file

@ -78,7 +78,7 @@ Supported options for **dump** include
**config** **config**
Output configuration data stored in the database. Each line Output configuration data stored in the database. Each line
starts with "#@ ", followed by a space seperated key-value starts with "#@ ", followed by a space separated key-value
pair. Both key and value are hex encoded if needed. pair. Both key and value are hex encoded if needed.
**tags** **tags**

4
doc/man1/notmuch-insert.rst
View file

@ -45,7 +45,7 @@ Supported options for **insert** include
Keep the message file if indexing fails, and keep the message Keep the message file if indexing fails, and keep the message
indexed if applying tags or maildir flag synchronization indexed if applying tags or maildir flag synchronization
fails. Ignore these errors and return exit status 0 to fails. Ignore these errors and return exit status 0 to
indicate succesful mail delivery. indicate successful mail delivery.
``--no-hooks`` ``--no-hooks``
Prevent hooks from being run. Prevent hooks from being run.
@ -53,7 +53,7 @@ Supported options for **insert** include
EXIT STATUS EXIT STATUS
=========== ===========
This command returns exit status 0 on succesful mail delivery, This command returns exit status 0 on successful mail delivery,
non-zero otherwise. The default is to indicate failed mail delivery on non-zero otherwise. The default is to indicate failed mail delivery on
any errors, including message file delivery to the filesystem, message any errors, including message file delivery to the filesystem, message
indexing to Notmuch database, changing tags, and synchronizing tags to indexing to Notmuch database, changing tags, and synchronizing tags to

2
doc/man1/notmuch-restore.rst
View file

@ -57,7 +57,7 @@ Supported options for **restore** include
**config** **config**
Restore configuration data to the database. Each configuration line starts Restore configuration data to the database. Each configuration line starts
with "#@ ", followed by a space seperated key-value pair. with "#@ ", followed by a space separated key-value pair.
Both key and value are hex encoded if needed. Both key and value are hex encoded if needed.
**tags** **tags**

2
doc/man5/notmuch-hooks.rst
View file

@ -41,7 +41,7 @@ The currently available hooks are described below.
message has been delivered, added to the database, and initial message has been delivered, added to the database, and initial
tags have been applied. The hook will not be run if there have tags have been applied. The hook will not be run if there have
been any errors during the message delivery; what is regarded been any errors during the message delivery; what is regarded
as succesful delivery depends on the ``--keep`` option. as successful delivery depends on the ``--keep`` option.
Typically this hook is used to perform additional query-based Typically this hook is used to perform additional query-based
tagging on the delivered messages. tagging on the delivered messages.