NEWS patches v2

NEWS patches v2

[David Bremner]

I had a series in progress more or less at the same time as Jani, so
of course there were all kinds of silly conflicts.

I rebased the two series together, and tried to get most of Tomi's formatting comments.

[PATCH 1/8] NEWS: news for initial revision tracking support (0.21)

[David Bremner]

---
 NEWS | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/NEWS b/NEWS
index 3593ded..019da55 100644
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,31 @@ General
 Notmuch now requires gmime >= 2.6.7. The gmime 2.4 series is no longer
 supported.
 
+Database revision tracking: `lastmod:` queries
+
+  Each message now has a metadata revision number that increases with
+  every tagging operation. See the discussion of `lastmod:` in
+  `notmuch-search-terms(7)` for more information.
+
+Notmuch database upgrade to support `lastmod:` queries
+
+  The above mentioned `lastmod:` prefix. This will be done
+  automatically, without prompting on the next time `notmuch new` is
+  run after the upgrade. The upgrade is not reversible, and the
+  upgraded database will not be readable by older versions of
+  Notmuch. As a safeguard, a database dump will be created in the
+  `.notmuch` directory before upgrading.
+
+Command Line Interface
+----------------------
+
+Database revision tracking
+
+  Two new options were added to support revision tracking. A global
+  option "--uuid" (`notmuch(1)`) was added for to detect counter
+  rollover and reinitialization, and `notmuch-count(1)` gained a
+  `--lastmod` option to query database revision tracking data.
+
 Emacs Interface
 ---------------
 
@@ -27,6 +52,12 @@ Library
 The use of absolute paths is now enforced when calling
 `notmuch_database_{open, create}`.
 
+Database revision tracking
+
+  Revision tracking is supported via a new prefix "lastmod:" in the
+  query parser and the new function
+  `notmuch_database_get_revision`. For the latter, see `notmuch(3)`.
+
 Notmuch 0.20.2 (2015-06-27)
 ===========================
 
-- 
2.5.3

[PATCH 2/8] NEWS: note some build system changes for 0.21

[David Bremner]

The ruby bindings changes in particular will be user visible. The
skipped tests status may also be interesting for packagers
---
 NEWS | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/NEWS b/NEWS
index 019da55..d35b8cd 100644
--- a/NEWS
+++ b/NEWS
@@ -22,6 +22,18 @@ Notmuch database upgrade to support `lastmod:` queries
   Notmuch. As a safeguard, a database dump will be created in the
   `.notmuch` directory before upgrading.
 
+Build System
+------------
+
+The ruby bindings are now built as part of the main notmuch build
+process. This can be disabled with the `--without-ruby` option to
+configure.
+
+Building the documentation can be disabled with the `--without-docs`
+option to configure.
+
+Skipped individual tests are no longer considered as failures.
+
 Command Line Interface
 ----------------------
 
-- 
2.5.3

[PATCH 3/8] NEWS: new count api / deprecated count/search functions for 0.21

[David Bremner]

---
 NEWS | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/NEWS b/NEWS
index d35b8cd..7f2f249 100644
--- a/NEWS
+++ b/NEWS
@@ -70,6 +70,15 @@ Database revision tracking
   query parser and the new function
   `notmuch_database_get_revision`. For the latter, see `notmuch(3)`.
 
+New status code returning API for n_query_count_{messages,threads}.
+
+Deprecated functions
+
+  `notmuch_query_search_threads`, `notmuch_query_search_messages`,
+  `notmuch_query_count_messages`, and `notmuch_query_count_threads`
+  are all deprecated as of this release.  Clients are encouraged to
+  transition to the `_st` variants supporting better error reporting.
+
 Notmuch 0.20.2 (2015-06-27)
 ===========================
 
-- 
2.5.3

[PATCH 4/8] NEWS: note some Emacs UI changes for 0.21

[David Bremner]

---
 NEWS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/NEWS b/NEWS
index 7f2f249..e2b3c62 100644
--- a/NEWS
+++ b/NEWS
@@ -58,6 +58,13 @@ Removed `notmuch-version` function by renaming it to `notmuch-cli-version`
   function which retrieves the version of `notmuch-command` is
   better named as `notmuch-cli-version`.
 
+Query input now supports completion for "is:<tag>".
+
+New message composition mode: `notmuch-compose-mode`
+
+  This is mainly to fix fcc handling, but may be useful for user
+  customization as well.
+
 Library
 -------
 
-- 
2.5.3

[PATCH 5/8] NEWS: nmbug-status supports sort order

[David Bremner]

From: Jani Nikula <jani@nikula.org>

---
 NEWS | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/NEWS b/NEWS
index e2b3c62..043da67 100644
--- a/NEWS
+++ b/NEWS
@@ -86,6 +86,11 @@ Deprecated functions
   are all deprecated as of this release.  Clients are encouraged to
   transition to the `_st` variants supporting better error reporting.
 
+nmbug-status
+------------
+
+nmbug-status now supports specifying the sort order for each view
+
 Notmuch 0.20.2 (2015-06-27)
 ===========================
 
-- 
2.5.3

[PATCH 6/8] NEWS: news for date:<expr>..!

[David Bremner]

From: Jani Nikula <jani@nikula.org>

---
 NEWS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/NEWS b/NEWS
index 043da67..647cd07 100644
--- a/NEWS
+++ b/NEWS
@@ -13,6 +13,13 @@ Database revision tracking: `lastmod:` queries
   every tagging operation. See the discussion of `lastmod:` in
   `notmuch-search-terms(7)` for more information.
 
+Date queries now support `date:<expr>..!` shorthand for
+`date:<expr>..<expr>`
+
+  You can use, for example, `date:yesterday..!` to match from the
+  beginning of yesterday to the end of yesterday. For further details,
+  please refer to the `notmuch-search-terms` manual page.
+
 Notmuch database upgrade to support `lastmod:` queries
 
   The above mentioned `lastmod:` prefix. This will be done
-- 
2.5.3

[PATCH 7/8] NEWS: news for notmuch address --deduplicate option

[David Bremner]

From: Jani Nikula <jani@nikula.org>

---
 NEWS | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/NEWS b/NEWS
index 647cd07..6a33330 100644
--- a/NEWS
+++ b/NEWS
@@ -51,6 +51,16 @@ Database revision tracking
   rollover and reinitialization, and `notmuch-count(1)` gained a
   `--lastmod` option to query database revision tracking data.
 
+The `notmuch address` command supports new deduplication schemes
+
+  `notmuch address` has gained a new `--deduplicate` option to specify
+  how the results should be deduplicated, if at all. The alternatives
+  are `no` (do not deduplicate, useful for processing the results with
+  external tools), `mailbox` (deduplicate based on the full, case
+  sensitive name and email address), and `address` (deduplicate based
+  on the case insensitive address part). See the `notmuch-address`
+  manual page for further information.
+
 Emacs Interface
 ---------------
 
-- 
2.5.3

[PATCH 8/8] NEWS: news for notmuch_directory_delete

[David Bremner]

From: Jani Nikula <jani@nikula.org>

---
 NEWS | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/NEWS b/NEWS
index 6a33330..c544a8e 100644
--- a/NEWS
+++ b/NEWS
@@ -88,6 +88,19 @@ Library
 The use of absolute paths is now enforced when calling
 `notmuch_database_{open, create}`.
 
+New function `notmuch_directory_delete` to delete directory documents
+
+  Previously there was no way to delete directory documents from the
+  database, leading to confusing results when the "ghost" directory
+  document of a renamed or deleted filesystem directory was
+  encountered every time the parent directory was being scanned by
+  `notmuch new`. The mtime of the old directory document was also used
+  if a directory by the same name was added again in the filesystem,
+  potentially bypassing the scan for the directory. The issues are
+  fixed by providing a library call to delete directory documents, and
+  deleting the old documents in `notmuch new` on filesystem directory
+  removal or rename.
+
 Database revision tracking
 
   Revision tracking is supported via a new prefix "lastmod:" in the
-- 
2.5.3

Re: NEWS patches v2

[Tomi Ollila]

On Sat, Oct 17 2015, David Bremner <david@tethera.net> wrote:

> I had a series in progress more or less at the same time as Jani, so
> of course there were all kinds of silly conflicts.
>
> I rebased the two series together, and tried to get most of Tomi's
> formatting comments.

From the formatting point of view this series looks good -- with luck
I don't have to do post-release NEWS formatting tunes this time(*) ;)

Jani: the tool to "check" formatting is devel/news2wiki.pl

(*) perhaps this time I have a chance (i.e. remember) to run
devel/news2wiki.pl *before* release.

Tomi

Re: NEWS patches v2

[Jani Nikula]

On Sun, 18 Oct 2015, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> On Sat, Oct 17 2015, David Bremner <david@tethera.net> wrote:
>
>> I had a series in progress more or less at the same time as Jani, so
>> of course there were all kinds of silly conflicts.
>>
>> I rebased the two series together, and tried to get most of Tomi's
>> formatting comments.
>
> From the formatting point of view this series looks good -- with luck
> I don't have to do post-release NEWS formatting tunes this time(*) ;)
>
> Jani: the tool to "check" formatting is devel/news2wiki.pl

Oh, but it doesn't complain on what I wrote, and then you have to check
whether the markdown output is all right or not... which is roughly
equivalent of manually checking the input?

BR,
Jani.

>
> (*) perhaps this time I have a chance (i.e. remember) to run
> devel/news2wiki.pl *before* release.
>
> Tomi

Re: NEWS patches v2

[Tomi Ollila]

On Sun, Oct 18 2015, Jani Nikula <jani@nikula.org> wrote:

> On Sun, 18 Oct 2015, Tomi Ollila <tomi.ollila@iki.fi> wrote:
>> On Sat, Oct 17 2015, David Bremner <david@tethera.net> wrote:
>>
>>> I had a series in progress more or less at the same time as Jani, so
>>> of course there were all kinds of silly conflicts.
>>>
>>> I rebased the two series together, and tried to get most of Tomi's
>>> formatting comments.
>>
>> From the formatting point of view this series looks good -- with luck
>> I don't have to do post-release NEWS formatting tunes this time(*) ;)
>>
>> Jani: the tool to "check" formatting is devel/news2wiki.pl
>
> Oh, but it doesn't complain on what I wrote, and then you have to check
> whether the markdown output is all right or not... which is roughly
> equivalent of manually checking the input?

Roughly ;p -- it is somewhat easier to look markdown than stare trailing
dots...

But yes, there is no tool to do any part of the checking automatically.
Perhaps the simplest one could be that if there is trailing dots in a
block that is not indented, write a message which informs that if the
line in question is supposed to be a header line, drop trailing dot...

Tomi


>
> BR,
> Jani.
>
>>
>> (*) perhaps this time I have a chance (i.e. remember) to run
>> devel/news2wiki.pl *before* release.
>>
>> Tomi