From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11667 invoked by alias); 8 Jun 2018 17:36:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 11657 invoked by uid 89); 8 Jun 2018 17:36:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: esa3.dell-outbound.iphmx.com Received: from esa3.dell-outbound.iphmx.com (HELO esa3.dell-outbound.iphmx.com) (68.232.153.94) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 08 Jun 2018 17:36:40 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FSAQBMvRpbh8uZ6ERdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQXDoEnCphYgX6WSgsjC4Q+AoJOITcVAQIBAQEBAQECAQECEAE?= =?us-ascii?q?BAQoLCQgpIwyCNSIRegEBAQEBAQEBAU0CDWMBAQEDATo/BQsCAQgYHhBXAgQOB?= =?us-ascii?q?YMiAoF3CA+sQ4hHgWMFCQGIOYITgTOCaIMRA4FfTIJlgiQCmHsHAoVtiH6BMIt?= =?us-ascii?q?4igaHJ4FXgXVwegGCGIIviGKFPm+QH4EZAQE?= X-IPAS-Result: =?us-ascii?q?A2FSAQBMvRpbh8uZ6ERdGQEBAQEBAQEBAQEBAQcBAQEBAYQ?= =?us-ascii?q?XDoEnCphYgX6WSgsjC4Q+AoJOITcVAQIBAQEBAQECAQECEAEBAQoLCQgpIwyCN?= =?us-ascii?q?SIRegEBAQEBAQEBAU0CDWMBAQEDATo/BQsCAQgYHhBXAgQOBYMiAoF3CA+sQ4h?= =?us-ascii?q?HgWMFCQGIOYITgTOCaIMRA4FfTIJlgiQCmHsHAoVtiH6BMIt4igaHJ4FXgXVwe?= =?us-ascii?q?gGCGIIviGKFPm+QH4EZAQE?= Received: from esa5.dell-outbound2.iphmx.com ([68.232.153.203]) by esa3.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2018 12:33:02 -0500 From: Received: from ausc60ps301.us.dell.com ([143.166.148.206]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2018 23:25:58 +0600 X-LoopCount0: from 10.166.135.76 X-DLP: DLP_GlobalPCIDSS To: CC: , Subject: Re: [PATCH] fix build failure with Python 3.7 Date: Fri, 08 Jun 2018 17:36:00 -0000 Message-ID: <96E0779A-AEB0-4A88-90B2-20E29EF493D6@dell.com> References: <96198491-96D8-42F0-9956-1C2BC9277050@dell.com> <87fu27fux2.fsf@redhat.com> <2BFDF702-C2E4-4339-ABB4-D0655063DE95@dell.com> <4e99c685-9047-bb84-8ead-ea13d4c202d3@redhat.com> <181F555B-4509-4DA2-9D10-4DF4D47D8E3F@dell.com> <1e718869-7d3d-11f3-1748-d7f34032c8d8@redhat.com> <44D6B060-1CF8-4285-9723-4EB503618855@dell.com> <5f0ab19d-02df-6462-7802-1dba8c0cf82e@redhat.com> <7EBB2FFE-48D7-4361-ACA8-A9CB87031CA6@dell.com> In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-ID: <702224EC0949C84EA131F76D39B2467B@dell.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2018-06/txt/msg00227.txt.bz2 > On Jun 8, 2018, at 10:55 AM, Pedro Alves wrote: >=20 > On 06/08/2018 03:37 PM, Paul.Koning@dell.com wrote: >=20 >>> Thanks. AFAICT, everything's sorted out. Anything holding this back? >>=20 >> Just waiting for approval to commit. >>=20 >=20 > Ah, but you already have it: >=20 > https://sourceware.org/ml/gdb-patches/2018-06/msg00015.html >=20 > Sorry if that wasn't clear. >=20 > Thanks, > Pedro Alves It was clear, but I managed to overlook the original message. I committed the patch with a commit message that references the original (R= ed Hat) bug. paul