--- /dev/null
+Return-Path: <jrollins@finestructure.net>\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 D5BBB429E37\r
+ for <notmuch@notmuchmail.org>; Wed, 4 Sep 2013 08:51:07 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_MED=-2.3] 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 Q2hagh2zXCSo for <notmuch@notmuchmail.org>;\r
+ Wed, 4 Sep 2013 08:51:01 -0700 (PDT)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+ [131.215.239.19])\r
+ by olra.theworths.org (Postfix) with ESMTP id 46D6F429E34\r
+ for <notmuch@notmuchmail.org>; Wed, 4 Sep 2013 08:51:01 -0700 (PDT)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+ by fire-doxen-postvirus (Postfix) with ESMTP id 702863280B5;\r
+ Wed, 4 Sep 2013 08:50:58 -0700 (PDT)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (unknown [198.129.209.144])\r
+ (Authenticated sender: jrollins)\r
+ by fire-doxen-submit (Postfix) with ESMTP id 1E1503280A2;\r
+ Wed, 4 Sep 2013 08:50:57 -0700 (PDT)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+ id 8C8306008B; Wed, 4 Sep 2013 08:50:56 -0700 (PDT)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Austin Clements <amdragon@MIT.EDU>,\r
+ Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: [PATCH v2] emacs: show: lazy part bugfix\r
+In-Reply-To: <20130904145639.GB1426@mit.edu>\r
+References: <1377246875-7784-1-git-send-email-markwalters1009@gmail.com>\r
+ <1378279835-28288-1-git-send-email-markwalters1009@gmail.com>\r
+ <20130904145639.GB1426@mit.edu>\r
+User-Agent: Notmuch/0.16+40~g62789b1 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Wed, 04 Sep 2013 08:50:39 -0700\r
+Message-ID: <87hae07fhs.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha256; protocol="application/pgp-signature"\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, 04 Sep 2013 15:51:08 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Wed, Sep 04 2013, Austin Clements <amdragon@MIT.EDU> wrote:\r
+>> Now, some mime parts have subparts and to avoid overwriting the\r
+>> sub-part data notmuch checks and if part data is already recorded it\r
+>> does not overwrite it.\r
+>>=20\r
+>> Now with lazy part handling this could fail: there is already part\r
+>> data stored. In the common case it works as the part type information\r
+>> was stored when the lazy-part button was inserted. However, this fails\r
+>> if the lazy part has sub-parts: notmuch had no idea these existed\r
+>> until the lazy part insertion.\r
+>\r
+> This says that things fail when a lazy part has sub-parts, but not\r
+> what the failure is. What is the failure? Can you give a specific\r
+> sequence of events and conditions that leads to and demonstrates the\r
+> failure?\r
+>\r
+> (I ask not just for commit posterity, but because I actually don't\r
+> know, though I may have figured it out after writing the comment\r
+> below.)\r
+\r
+Hey, Austin. Here's an example of a mail that is effected the issue:\r
+\r
+=E2=94=94=E2=94=AC=E2=95=B4multipart/alternative 896783 bytes\r
+ =E2=94=9C=E2=94=80=E2=95=B4text/plain 379 bytes\r
+ =E2=94=94=E2=94=AC=E2=95=B4multipart/related 892556 bytes\r
+ =E2=94=9C=E2=94=80=E2=95=B4text/html 1236 bytes\r
+ =E2=94=94=E2=94=80=E2=95=B4image/jpeg inline [photo.JPG] 890841 bytes\r
+\r
+The multipart/related part is initially hidden. Without Istvan's patch,\r
+there would be no button at all for the image/jpeg part, even when the\r
+multipart/related is exposed. With Istvan's patch the image/jpeg button\r
+is there, but without Mark's patch the button would actually reference\r
+the entire multipart/alternative part, instead of just the image/jpeg.\r
+If I tried to save the image/jpeg I would get the entire\r
+multipart/alternative mime structure in plain text.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.14 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJSJ1bQAAoJEO00zqvie6q8DRQQALfbe4fmzvB+HZYcet9h0kNX\r
+oqdnEH2ePCDl61BdRc22IvbeQK3IyGmzn6ICI57p5crgEQUOJtmY4Bw3zE2UWIIn\r
+cxlY5OXfnY2nojlNE1x58WbufXsxcJ8xlxzhnjJvX6F13jYv+0puXlH1pOwglqWi\r
+c+FMonWdTJSGvL6PxZJum+uVQI/8Z6GMZ+jeIDRDyw/R5JRfqFyYsEnx3YQub340\r
+w7KKzG7kHhYz3BFWcVj1aJ3zGKNYAzLHn7rPIU+3snmGTHdWkp433RakBZdF5Qfy\r
+z0Zwk6EkSPQSFsPpqBus7vKZ1MKgA6qHg+Kals6a3X5nsMmFVxPfdukkGMMU7Oj3\r
+KNIZyi1HoHKWkTtkx3xlCbj0slcX+/ViS0SK9N5wNEsgTR3iXJjc8zOcTksqn2db\r
+aSc6cBAYLhybNGrSKHJmWBu2EJmh02alwEbvgbIyPTV7lD5gK1j3TjBNy674Mp9U\r
+EIQ9U6LtzOyErtvIVpLxO8p6Ai6ieVDv9IUCGEbKAbPUH2Ml8666MrIn7tmRWeuE\r
+IwG0CMySDTQq9Wrou5fhyGdPpWyYk70wVhmOcl3W0oopoKVm5Remnb3G340eBSDe\r
+PMkzet743gzcw78R8/18s1gkvM4DE2exvQOaCVYqIOJRNIH0UyJ3zomJKlcE6UeP\r
+JA2Y46V+tlY4jiHMKjil\r
+=C6rI\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff