Re: [PATCH] Output unmodified Content-Type header value for JSON format.

diff --git a/bc/3a52f1fb7a6c82eedf6438910022cb83116bdb b/bc/3a52f1fb7a6c82eedf6438910022cb83116bdb
new file mode 100644 (file)
index 0000000..732547d
--- /dev/null
+++ b/bc/3a52f1fb7a6c82eedf6438910022cb83116bdb
@@ -0,0 +1,91 @@
+Return-Path: <amdragon@mit.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 7647A429E2F\r
+       for <notmuch@notmuchmail.org>; Tue, 22 Nov 2011 19:38:03 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id DDJKXhBoXDqr for <notmuch@notmuchmail.org>;\r
+       Tue, 22 Nov 2011 19:38:03 -0800 (PST)\r
+Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU\r
+       [18.7.68.35])\r
+       by olra.theworths.org (Postfix) with ESMTP id 0367B431FB6\r
+       for <notmuch@notmuchmail.org>; Tue, 22 Nov 2011 19:38:02 -0800 (PST)\r
+X-AuditID: 12074423-b7f266d0000008b8-ea-4ecc6a9a1d1b\r
+Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])\r
+       by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id 5A.AE.02232.A9A6CCE4; Tue, 22 Nov 2011 22:38:02 -0500 (EST)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+       by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id pAN3c2Zd004353; \r
+       Tue, 22 Nov 2011 22:38:02 -0500\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+       (authenticated bits=0)\r
+       (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+       by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id pAN3c1NU009131\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+       Tue, 22 Nov 2011 22:38:01 -0500 (EST)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1RT3h7-0006wg-R7; Tue, 22 Nov 2011 22:40:21 -0500\r
+Date: Tue, 22 Nov 2011 22:40:21 -0500\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>\r
+Subject: Re: [PATCH] Output unmodified Content-Type header value for JSON\r
+       format.\r
+Message-ID: <20111123034021.GL9351@mit.edu>\r
+References: <1321659905-24367-1-git-send-email-dmitry.kurochkin@gmail.com>\r
+       <87fwhkyisj.fsf@servo.finestructure.net> <87wrawq1dz.fsf@gmail.com>\r
+       <87d3coxu7s.fsf@servo.finestructure.net> <87r512pru2.fsf@gmail.com>\r
+       <87ipmewo4z.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87ipmewo4z.fsf@servo.finestructure.net>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFuplleLIzCtJLcpLzFFi42IR4hTV1p2VdcbP4M1RNYurW/vZLfbs87K4\r
+       fnMmswOzx93TXB47Z91l93i26hZzAHMUl01Kak5mWWqRvl0CV8axg+sZC76wVCxc8J+xgfEn\r
+       cxcjJ4eEgInEz2O3mCBsMYkL99azdTFycQgJ7GOU6F8yjwnC2cAo0fHrMQuEc5JJ4tW281Bl\r
+       Sxgl3h+YB9bPIqAqce7HEXYQm01AQ2Lb/uWMILaIgJlEz5c/YDazgJfEhE+nwOqFBYIlXi5r\r
+       B7N5BbQlWme8YIUY2sok0Xr8ADtEQlDi5MwnLBDNWhI3/r0EauAAsqUllv/jAAlzCphKHHxx\r
+       AGyOqICKxJST29gmMArNQtI9C0n3LITuBYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3TN9HIz\r
+       S/RSU0o3MYJCnd1FeQfjn4NKhxgFOBiVeHgjT572E2JNLCuuzD3EKMnBpCTKq5h5xk+ILyk/\r
+       pTIjsTgjvqg0J7X4EKMEB7OSCO81d6Acb0piZVVqUT5MSpqDRUmcV2ang5+QQHpiSWp2ampB\r
+       ahFMVoaDQ0mCd2o8UKNgUWp6akVaZk4JQpqJgxNkOA/Q8Ksgi3mLCxJzizPTIfKnGBWlxHn3\r
+       giQEQBIZpXlwvbBU9IpRHOgVYd5mkBU8wDQG1/0KaDAT0OBpa0+ADC5JREhJNTDqp7J0MGUq\r
+       sb+MYP2y6YJ2mffZciPdD5ndDIsmCi+ZfZk1f+2kt/b7Pl3/uqvcOPzE9klsi8SvmwW27Dy1\r
+       5vnzRRLxxd1h3Af+2fEUnf7oXzp3wTXLmow+Pt2eiRxGNSlb19a/81+0f1lURfPR9w9/Trp+\r
+       4uUimTPHJ7wNfbcmo0F93bQfvl9WK7EUZyQaajEXFScCAPK0U3EgAwAA\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 23 Nov 2011 03:38:03 -0000\r
+\r
+Quoth Jameson Graef Rollins on Nov 20 at 12:10 pm:\r
+> The open question seems to be how we handle the content encoding\r
+> parameters.  My argument is that those should either be used by notmuch\r
+> to properly encode the content for the consumer.  If that's not\r
+> possible, then just those parameters needed by the consumer to decode\r
+> the content should be output.\r
+\r
+If notmuch is going to include part content in the JSON output (which\r
+perhaps it shouldn't, as per recent IRC discussions), then it must\r
+handle content encodings because JSON must be Unicode and therefore\r
+the content strings in the JSON must be Unicode.\r