notmuch/lib/message.cc, branch 0.23.5thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.23.52016-09-21T21:14:24Zlib: basic message-property API2016-09-21T21:14:24ZDavid Bremnerdavid@tethera.net2016-06-13T01:05:50Zurn:sha1:b8bb6d796458732622f80464dd808b3e02f57d9d
Initially, support get, set and removal of single key/value pair, as
well as removing all properties.
lib: read "property" terms from messages.2016-09-21T21:14:24ZDavid Bremnerdavid@tethera.net2016-06-13T01:05:48Zurn:sha1:4dfb69169e6b685670ebdeedab898c31adc995b2
This is a first step towards providing an API to attach
arbitrary (key,value) pairs to messages and retrieve all of the values
for a given key.
Use https instead of http where possible2016-06-05T11:32:17ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-06-02T16:26:14Zurn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb
Many of the external links found in the notmuch source can be resolved
using https instead of http. This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
lib: whitespace cleanup2016-06-05T11:23:28ZTomi Ollilatomi.ollila@iki.fi2016-05-28T17:45:31Zurn:sha1:cf09631a45d276826255d197c1d5c913a29c79f4
Cleaned the following whitespace in lib/* files:
lib/index.cc: 1 line: trailing whitespace
lib/database.cc 5 lines: 8 spaces at the beginning of line
lib/notmuch-private.h: 4 lines: 8 spaces at the beginning of line
lib/message.cc: 1 line: trailing whitespace
lib/sha1.c: 1 line: empty lines at the end of file
lib/query.cc: 2 lines: 8 spaces at the beginning of line
lib/gen-version-script.sh: 1 line: trailing whitespace
complete ghost-on-removal-when-shared-thread-exists2016-04-15T10:13:49ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-04-09T01:54:52Zurn:sha1:e366bb222722d6a635b736e875b760d82b46d1f5
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 thread2016-04-15T10:07:23ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-04-09T01:54:51Zurn:sha1:1695415039803fd3b317bccbb3ceca0472bed373
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:23ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-04-09T01:54:50Zurn:sha1:9eebae3da4510a671cbbb2f476c2dc04099b4415
It can be useful to easily tell if a given message has a given term
associated with it.
fix thread breakage via ghost-on-removal2016-04-15T10:07:23ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-04-09T01:54:48Zurn:sha1:604d1e0977c2ede365f87492d6b9bf9a83c3e1d3
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.
clean up stray apostrophe in comment2016-01-16T12:17:15ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-01-15T05:23:10Zurn:sha1:07b6220a5595bf4556e636709220121d6405e9e9
This is a nit-picky orthographical fix for an nit-picky ontological
comment.
correct comment referring to notmuch_database_remove_message2016-01-16T12:16:51ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-01-15T19:02:38Zurn:sha1:e038b95ffe18b13fb47f4982ddc969669172cb32
notmuch_database_remove_message has no leading underscore in its name.