From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3512 invoked by alias); 1 Jun 2018 13:47:33 -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 3375 invoked by uid 89); 1 Jun 2018 13:47:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:679 X-HELO: esa1.dell-outbound.iphmx.com Received: from esa1.dell-outbound.iphmx.com (HELO esa1.dell-outbound.iphmx.com) (68.232.153.90) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Jun 2018 13:47:30 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EiAQAOThFbh8qZ6ERcGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQXDoEnCphYgXmWRAsjC4Q+AoIGITcVAQIBAQEBAQECAQECEAE?= =?us-ascii?q?BAQoLCQgoIwyCNSIRS1wBAQEBAQEjAg1jAQEBAwE6PwULAgEIGB4QVwIEDgWDI?= =?us-ascii?q?gKBdwgPqFOIQIFjBQkBiDSCE4EzgmmDEQQYghKCZIIkAphrBwKFbIh1CoEki2a?= =?us-ascii?q?JcYcmgVeBdXB6AYIYgi6IYoU+b49NgRkBAQ?= X-IPAS-Result: =?us-ascii?q?A2EiAQAOThFbh8qZ6ERcGQEBAQEBAQEBAQEBAQcBAQEBAYQ?= =?us-ascii?q?XDoEnCphYgXmWRAsjC4Q+AoIGITcVAQIBAQEBAQECAQECEAEBAQoLCQgoIwyCN?= =?us-ascii?q?SIRS1wBAQEBAQEjAg1jAQEBAwE6PwULAgEIGB4QVwIEDgWDIgKBdwgPqFOIQIF?= =?us-ascii?q?jBQkBiDSCE4EzgmmDEQQYghKCZIIkAphrBwKFbIh1CoEki2aJcYcmgVeBdXB6A?= =?us-ascii?q?YIYgi6IYoU+b49NgRkBAQ?= Received: from esa2.dell-outbound2.iphmx.com ([68.232.153.202]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jun 2018 08:40:35 -0500 From: Received: from ausxippc110.us.dell.com ([143.166.85.200]) by esa2.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jun 2018 19:44:00 +0600 X-LoopCount0: from 10.166.136.210 X-DLP: DLP_GlobalPCIDSS To: CC: , Subject: Re: [PATCH] fix build failure with Python 3.7 Date: Fri, 01 Jun 2018 13:47:00 -0000 Message-ID: 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> In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-ID: <7616C86E89FC2A4CB08D94EAE21A30A0@dell.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2018-06/txt/msg00017.txt.bz2 > On Jun 1, 2018, at 9:37 AM, Pedro Alves wrote: >=20 > On 06/01/2018 02:36 PM, Pedro Alves wrote: >> On 06/01/2018 02:22 PM, Paul.Koning@dell.com wrote: >>> Ok, here is the patch in its current state. Ok to commit? >>=20 >> Yes, but recall to include the rationale in the git commit log, and >> to include the link to the original Python issue in there. >=20 > Actually, should this go to the 8.1 branch too? If so, then per > standard procedure we will indeed need a GDB bugzilla bug filed > (and then a reference added to the ChangeLog). I opened the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D23252 paul