notmuch, branch 0.22_rc0

debian: minimal changelog for 0.22~rc0-1

2016-04-16T11:45:56Z

version: bump to 0.22~rc0

2016-04-16T11:44:39Z

bindings: drop build time message on missing ruby dependency

2016-04-16T11:26:40Z

The usual make message on everything being up to date is: make: Nothing to be done for 'all'. However, since commit d038b9320949c79503fe4b76870aaabf279405ab Author: David Bremner Date: Mon Jun 1 09:08:59 2015 +0200 build: integrate building ruby bindings into notmuch build process if one doesn't have the ruby dependencies installed, the message has been: Missing dependency, skipping ruby bindings Restore the usual behaviour by dropping the message. It's redundant during build anyway, since the configure script already outputs: Checking for ruby development files... No (skipping ruby bindings)

emacs: Add notmuch homepage to package header

2016-04-16T11:25:10Z

So user can find out notmuch's homepage with: C-h P ('describe-package') notmuch

emacs: Fix packaging

2016-04-16T11:24:42Z

Refer to (info "(elisp) Library Headers") for package conventions.

complete ghost-on-removal-when-shared-thread-exists

2016-04-15T10:13:49Z

To fully complete the ghost-on-removal-when-shared-thread-exists proposal, we need to clear all ghost messages when the last active message is removed from a thread. Amended by db: Remove the last test of T530, as it no longer makes sense if we are garbage collecting ghost messages.

On deletion, replace with ghost when other active messages in thread

2016-04-15T10:07:23Z

There is no need to add a ghost message upon deletion if there are no other active messages in the thread. Also, if the message being deleted was a ghost already, we can just go ahead and delete it.

Introduce _notmuch_message_has_term()

2016-04-15T10:07:23Z

It can be useful to easily tell if a given message has a given term associated with it.

Add internal functions to search for alternate doc types

2016-04-15T10:07:23Z

Publicly we are only exposing the non-ghost documents (of "type" "mail"). But internally we might want to inspect the ghost messages as well. This changeset adds two new private interfaces to queries to recover information about alternate document types.

fix thread breakage via ghost-on-removal

2016-04-15T10:07:23Z

implement ghost-on-removal, the solution to T590-thread-breakage.sh that just adds a ghost message after removing each message. It leaks information about whether we've ever seen a given message id, but it's a fairly simple implementation. Note that _resolve_message_id_to_thread_id already introduces new message_ids to the database, so i think just searching for a given message ID may introduce the same metadata leakage.