From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 369486DE2E46 for ; Sat, 15 Jul 2017 04:47:23 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elAEj3Qur5tk for ; Sat, 15 Jul 2017 04:47:22 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 7F4BB6DE2E41 for ; Sat, 15 Jul 2017 04:47:22 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dWLUP-0005Aj-So; Sat, 15 Jul 2017 07:44:01 -0400 Received: (nullmailer pid 4465 invoked by uid 1000); Sat, 15 Jul 2017 11:47:18 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: [PATCH] Avoid crashes in "notmuch reply" with gmime 3.0 when reply-to == sender In-Reply-To: <87wp7ask9k.fsf@fifthhorseman.net> References: <20170714201423.19688-2-dkg@fifthhorseman.net> <20170714220335.17884-1-dkg@fifthhorseman.net> <871spiu0oc.fsf@fifthhorseman.net> <87wp7ask9k.fsf@fifthhorseman.net> Date: Sat, 15 Jul 2017 08:47:18 -0300 Message-ID: <87shhxdird.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2017 11:47:23 -0000 Daniel Kahn Gillmor writes: > On Sat 2017-07-15 00:13:39 +0200, Daniel Kahn Gillmor wrote: >> I'm currently publishing it currently on the gmime 3.0 branch (commit id >> aeeded4307162bdc1c745d15cd3ccf5a2140bdf9) at >> https://gitlab.com/dkg/notmuch if anyone wants to consider it (i'm >> likely to rebase all non-master branches on that repo, though, so please >> don't necessarily rely on their stability) > > Sorry: that's the "gmime3.0" branch, and the current commit ID (after a > bit more cleanup) is: 37c4f458b18f29a7ead679912b0982c266030b7c > > That's currently a 19-patch series (many of which came from bremner's > gmime 3.0 porting series, with some intervening patches), which i'm > happy to re-post here if it'll help people review. > I've pushed my own reconstruction of this, which - drops one patch of my own series -- id:20170603174754.16911-11-david@tethera.net as discussed before, it's not clear that this will ever be fixed in GMime, or that it's a real problem for users. - leaves off for now the last patch in your crypto related series id:20170714131202.24966-3-dkg@fifthhorseman.net I'll comment in that thread about that patch.