NEWS: mention message properties API, dump/restore

[notmuch] / NEWS

diff --git a/NEWS b/NEWS
index f6ecbc7635096089516611e7513c125d7640ee40..5590bb813da9848b999e4f65edf8942c79a20b43 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -21,6 +21,20 @@ Support for named queries
   `query:name` format. The expansion of these queries is stored in the
   database and they can be used from any notmuch client.
 
+Library
+-------
+
+Message property API
+
+  libnotmuch now supports the attachment of arbitrary key-value pairs
+  to messages. These can be used by various tools to manage their
+  private data without polluting the user tag space. They also support
+  iteration of values with the same key or same key prefix.
+
+Bug fix for `notmuch_directory_set_mtime`
+
+  Update cached mtime to match on-disk mtime.
+
 CLI
 ---
 
@@ -30,12 +44,13 @@ Support for compile time options
   config. Initial keys in this group are `compact`, `field_processor`,
   and `retry_lock`.
 
-Dump/Restore support for configuration information
+Dump/Restore support for configuration information and properties
 
   Any configuration information stored in the database (initially just
-  named queries) is dumped and restored. Any new information in the
-  dump format is prefixed by '#' to allow existing scripts to ignore
-  it.
+  named queries) is dumped and restored. Similarly any properties
+  attached to messages are also dumped and restored. Any new
+  information in the dump format is prefixed by '#' to allow existing
+  scripts to ignore it.
 
 Emacs
 -----
@@ -47,6 +62,8 @@ Face customization is easier
   `notmuch-search-flagged-face` and `notmuch-search-unread-face` are
   now used by default. Customize `notmuch-faces` to modify them.
 
+Omit User-Agent header by default when sending mail
+
 Ruby Bindings
 -------------
 
@@ -59,10 +76,10 @@ Go bindings moved to contrib
 
 Add support for `notmuch_threads_t` and `notmuch_thread_t`
 
-Fixed constant values so they are not all zero anymore.
+Fixed constant values so they are not all zero anymore
 
   Previously, it was impossible to open writable database handles,
-  because DATABASE_MODE_READ_ONLY and DATABASE_MODE_READ_WRITE were
+  because `DATABASE_MODE_READ_ONLY` and `DATABASE_MODE_READ_WRITE` were
   both set to zero.
   The same issue occured with sort modes.