aboutsummaryrefslogtreecommitdiffhomepage
path: root/test/corpus/cur/11:2,
diff options
context:
space:
mode:
authorGravatar Carl Worth <cworth@cworth.org>2010-11-11 04:17:29 -0800
committerGravatar Carl Worth <cworth@cworth.org>2010-11-11 04:17:29 -0800
commitf6ec7ca78f867c2ae27d0dba154a2395ccf15f52 (patch)
treeb6c368c1de94340c1417c284cac8909e7576252c /test/corpus/cur/11:2,
parent666e410b60855dd714c2b4f36085aeae1810907c (diff)
test: Move corpus emails into maildir directory structure
Now that we have maildir synchronization turned on by default, it's advantageous to make all of the tests exercise it as much as possible.
Diffstat (limited to 'test/corpus/cur/11:2,')
-rw-r--r--test/corpus/cur/11:2,27
1 files changed, 27 insertions, 0 deletions
diff --git a/test/corpus/cur/11:2, b/test/corpus/cur/11:2,
new file mode 100644
index 00000000..c0701def
--- /dev/null
+++ b/test/corpus/cur/11:2,
@@ -0,0 +1,27 @@
+From: "Keith Packard" <keithp@keithp.com>
+To: notmuch@notmuchmail.org
+Date: Tue, 17 Nov 2009 13:15:25 -0800
+Subject: [notmuch] [PATCH 1/2] Close message file after parsing message
+ headers
+In-Reply-To: <87lji5cbwo.fsf@yoom.home.cworth.org>
+References: <1258471718-6781-1-git-send-email-dottedmag@dottedmag.net>
+ <87lji5cbwo.fsf@yoom.home.cworth.org>
+Message-ID: <yunbpj0etua.fsf@aiko.keithp.com>
+
+On Tue, 17 Nov 2009 09:13:27 -0800, Carl Worth <cworth at cworth.org> wrote:
+
+> I didn't apply Keith's fix yet, because I think I'd rather just fix the
+> indexer to store the In-Reply-To header in a separate term prefix from
+> the term used for the References header[*]. That will then let us lookup
+> the in-reply-to value later for thread constructions without having to
+> open the original email file at all.
+
+Threading the message also involves displaying the from and to contents,
+which requires opening the message file. The alternative to the fix I
+provided is to just parse all of the message headers when first opening
+the message; it could then be immediately closed and the hash referred
+to for all header data. Given the choice, just having the caller say
+when it has finished with a message is probably a reasonable option...
+
+-keith
+