fix thread breakage via ghost-on-removal
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Sat, 9 Apr 2016 01:54:48 +0000 (22:54 -0300)
committerDavid Bremner <david@tethera.net>
Fri, 15 Apr 2016 10:07:23 +0000 (07:07 -0300)
commit604d1e0977c2ede365f87492d6b9bf9a83c3e1d3
tree4b54122413b1d49543345366782256bdd3e531a6
parent92559ee3473381b0ba207ddb7db944d6ffadc2db
fix thread breakage via ghost-on-removal

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.
lib/message.cc
test/T590-thread-breakage.sh