revisision tracking patches round 3

Ironically there is some uncertainty about what revision this is due to confusing cover letters for previous rounds. This obsoletes id:1433525318-23756-1-git-send-email-da...@tethera.net I think I've taken into account most (all?) of Tomi and Daniel's comments. There was a fair amount of

[PATCH 2/5] lib: API to retrieve database revision and UUID

From: Austin Clements acleme...@csail.mit.edu This exposes the committed database revision to library users along with a UUID that can be used to detect when revision numbers are no longer comparable (e.g., because the database has been replaced). --- lib/database-private.h | 1 +

[PATCH 3/5] cli/count: add --output=modifications

We need some way to extract the uuid/revision of the database, and count seems like the least bad choice of current commands. The (perhaps weak) argument for count over search is that count already reports statistics about the entire database. --- notmuch-count.c| 18

[PATCH 4/5] cli: add global option --uuid

The function notmuch_exit_if_unmatched_db_uuid is split from notmuch_process_shared_options because it needs an open notmuch database. --- doc/man1/notmuch.rst | 12 ++-- notmuch-client.h | 4 notmuch-compact.c | 4 notmuch-config.c

[PATCH 5/5] lib: Add lastmod: queries for filtering by last modification

From: Austin Clements amdra...@mit.edu The implementation is essentially the same as the date range search prior to Jani's fancy date parser. --- doc/man7/notmuch-search-terms.rst | 8 lib/database-private.h| 1 + lib/database.cc | 4

[PATCH 1/5] lib: Add per-message last modification tracking

From: Austin Clements amdra...@mit.edu This adds a new document value that stores the revision of the last modification to message metadata, where the revision number increases monotonically with each database commit. An alternative would be to store the wall-clock time of the last modification

[PATCH] build: extract library versions from notmuch.h

- Make lib/notmuch.h the canonical location for the library versioning information. - Since the release-check should never fail now, remove it to reduce complexity. - Make the version numbers in notmuch.h consistent with the (now deleted) ones in lib/Makefile.local --- Not counting turning 20

tags vs. show

I'm having a problem with notmuch show producing too many results. Can somebody tell me how to notmuch show only emails that a specific tag? Specifics (linux mint, emacs 24.3.1): I run this tagging query at the command line: notmuch tag +xyz -- '(to:x...@me.com or from:x...@me.com or

Re: [PATCH] build: extract library versions from notmuch.h

On Sun, Aug 09 2015, David Bremner da...@tethera.net wrote: - Make lib/notmuch.h the canonical location for the library versioning information. - Since the release-check should never fail now, remove it to reduce complexity. - Make the version numbers in notmuch.h consistent with the (now

Re: tags vs. show

Paul Tarvydas paultarvy...@gmail.com writes: Specifics (linux mint, emacs 24.3.1): What version of notmuch? I run this tagging query at the command line: notmuch tag +xyz -- '(to:x...@me.com or from:x...@me.com or cc:x...@me.com)' fwiw, cc: is not a valid search prefix, but I don't

revisision tracking patches round 3

Ironically there is some uncertainty about what revision this is due to confusing cover letters for previous rounds. This obsoletes id:1433525318-23756-1-git-send-email-david at tethera.net I think I've taken into account most (all?) of Tomi and Daniel's comments. There was a fair amount

[PATCH 2/5] lib: API to retrieve database revision and UUID

From: Austin Clements This exposes the committed database revision to library users along with a UUID that can be used to detect when revision numbers are no longer comparable (e.g., because the database has been replaced). --- lib/database-private.h | 1 +

[PATCH 3/5] cli/count: add --output=modifications

We need some way to extract the uuid/revision of the database, and count seems like the least bad choice of current commands. The (perhaps weak) argument for count over search is that count already reports statistics about the entire database. --- notmuch-count.c| 18

[PATCH 4/5] cli: add global option "--uuid"

The function notmuch_exit_if_unmatched_db_uuid is split from notmuch_process_shared_options because it needs an open notmuch database. --- doc/man1/notmuch.rst | 12 ++-- notmuch-client.h | 4 notmuch-compact.c | 4 notmuch-config.c

[PATCH 5/5] lib: Add "lastmod:" queries for filtering by last modification

From: Austin Clements The implementation is essentially the same as the date range search prior to Jani's fancy date parser. --- doc/man7/notmuch-search-terms.rst | 8 lib/database-private.h| 1 + lib/database.cc | 4

[PATCH 1/5] lib: Add per-message last modification tracking

From: Austin Clements This adds a new document value that stores the revision of the last modification to message metadata, where the revision number increases monotonically with each database commit. An alternative would be to store the wall-clock time of the last

[PATCH] build: extract library versions from notmuch.h

- Make lib/notmuch.h the canonical location for the library versioning information. - Since the release-check should never fail now, remove it to reduce complexity. - Make the version numbers in notmuch.h consistent with the (now deleted) ones in lib/Makefile.local --- Not counting turning 20