X-Git-Url: https://git.notmuchmail.org/git?p=notmuch;a=blobdiff_plain;f=test%2Fcorpus%2F40;fp=test%2Fcorpus%2F40;h=0000000000000000000000000000000000000000;hp=91a15a8d74102e6b2d8c774bd76a709f67bc9860;hb=f6ec7ca78f867c2ae27d0dba154a2395ccf15f52;hpb=666e410b60855dd714c2b4f36085aeae1810907c diff --git a/test/corpus/40 b/test/corpus/40 deleted file mode 100644 index 91a15a8d..00000000 --- a/test/corpus/40 +++ /dev/null @@ -1,31 +0,0 @@ -From: "Carl Worth" -To: notmuch@notmuchmail.org -Date: Wed, 18 Nov 2009 01:42:02 -0800 -Subject: [notmuch] [PATCH 1/2] Close message file after parsing message - headers -In-Reply-To: -References: <1258471718-6781-1-git-send-email-dottedmag@dottedmag.net> - <87lji5cbwo.fsf@yoom.home.cworth.org> -Message-ID: <87pr7gqidx.fsf@yoom.home.cworth.org> - -On Tue, 17 Nov 2009 13:15:25 -0800, Keith Packard wrote: -> 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... - -Hi Keith, - -Once I finally got back on the ground again, I pushed out a revised -version of your patch, (didn't need the reply-to stuff anymore since I -had fixed that differently in the meantime). - -I'm pretty happy with the state of this portion of the code now. - -Thanks Keith and Mikhail for your input on and code to fix this bug. - --Carl - -