diff options
author | Carl Worth <cworth@cworth.org> | 2010-11-10 17:45:59 -0800 |
---|---|---|
committer | Carl Worth <cworth@cworth.org> | 2010-11-11 03:40:19 -0800 |
commit | d422dcf0a276f2806d5563fbdc48fa7d69e4c3eb (patch) | |
tree | 233251d05b36a11309579bbc3f955f0cb470c9b6 /lib/database.cc | |
parent | bb74e9dff80e64734308d5997c756fd96d041235 (diff) |
lib: Remove the notion of TAGS_INVALID
This rather ugly hack was recently obviated by the removal of the
notmuch_database_set_maildir_sync function. Now, clients must make
explicit calls to do any syncrhonization between maildir flags and
tags. So the library no longer needs to worry about doing inconsistent
synchronization while a message is only partially added.
Diffstat (limited to 'lib/database.cc')
-rw-r--r-- | lib/database.cc | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/lib/database.cc b/lib/database.cc index 380bbe3..7a00917 100644 --- a/lib/database.cc +++ b/lib/database.cc @@ -1642,13 +1642,6 @@ notmuch_database_add_message (notmuch_database_t *notmuch, _notmuch_message_add_filename (message, filename); - /* This is a new message or it has a new filename and as such, - * its tags in database either do not exists or might be out - * of date. We assign the tags later in notmuch new, but until - * then we should not synchronize the tags back to the maildir - * flags (if notmuch is configured to do so). */ - notmuch_message_set_flag(message, NOTMUCH_MESSAGE_FLAG_TAGS_INVALID, TRUE); - /* Is this a newly created message object? */ if (private_status == NOTMUCH_PRIVATE_STATUS_NO_DOCUMENT_FOUND) { _notmuch_message_add_term (message, "type", "mail"); |