From 6ccdffcd87b8af0c1c683588612169f5dc776644 Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Fri, 23 Oct 2009 06:00:10 -0700 Subject: add_message: Fix to not add multiple documents with the same message ID Here's the second big fix to message-ID handling, (the first was to generate message IDs when an email contained none). Now, with no document missing a message ID, and no two documents having the same message ID, we have a nice consistent database where the message ID can be used as a unique key. --- notmuch-private.h | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'notmuch-private.h') diff --git a/notmuch-private.h b/notmuch-private.h index 4910311..8b317c2 100644 --- a/notmuch-private.h +++ b/notmuch-private.h @@ -107,18 +107,6 @@ _notmuch_message_create_for_message_id (const void *talloc_owner, notmuch_database_t *notmuch, const char *message_id); -/* XXX: Here temporarily during code movement only. */ -/* "128 bits of thread-id ought to be enough for anybody" */ -#define NOTMUCH_THREAD_ID_BITS 128 -#define NOTMUCH_THREAD_ID_DIGITS (NOTMUCH_THREAD_ID_BITS / 4) -typedef struct _thread_id { - char str[NOTMUCH_THREAD_ID_DIGITS + 1]; -} thread_id_t; - - -void -thread_id_generate (thread_id_t *thread_id); - /* Lookup a prefix value by name. * * XXX: This should really be static inside of message.cc, and we can -- cgit v1.2.3