From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5212 invoked by alias); 1 Jun 2018 11:58:10 -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 5188 invoked by uid 89); 1 Jun 2018 11:58:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=PaulKoningdellcom, sk:paulko, sk:Paul.Ko, sk:paul.ko X-HELO: mail-wm0-f65.google.com Received: from mail-wm0-f65.google.com (HELO mail-wm0-f65.google.com) (74.125.82.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Jun 2018 11:58:08 +0000 Received: by mail-wm0-f65.google.com with SMTP id t11-v6so2567619wmt.0 for ; Fri, 01 Jun 2018 04:58:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=I/XM9TncJZhPze2UPKkfnk5GyH/Hqe4tXNIB7xt0l+U=; b=gaqyyDF5nbf1ndgbM3FJtBiyjBKJcy9F3zgzUL97F9XlV/MKRMMRWHnJrrs1J74z83 8NhWtqmCWDshsrGf3/5k82WBot9UkX5wMfdnqCjO8jlKpJysShvidtR5Cc3uzyjE1rwO R8tYKdWEK7z+wjJ8eDFfGoR3Rs6T7OEOy8k9la77R2iXojEtMbzPFfF5SEhTtlfdq4+G adKwoUY5AFxDYRRADcfZBAyWzJEwdhY87Ak5HPI+YK2ILUT1RYaoJJrcB1F53e8Jp6J3 oKI7kF05/Y/iN4nxyonRsJoFQYFFp1Ss+89usZB5gyRbpcpC7MBBuzO6H1bd0s/Xi8R6 WAxw== X-Gm-Message-State: APt69E1p2VlPGF6WiN1ZlP8tgDj8zzIDE/6FoHqZzC/b0BrzmD3PDN48 aiBmSbGXk911+0YNxqfOOTSN2uTpkSo= X-Google-Smtp-Source: ADUXVKKr7VfdNeDAX4RkcglKYRuHOoyaLUobdLopkyYmddUEKw2GGKXxqOKtgG6HMCEUpVj/rZGTKw== X-Received: by 2002:a1c:d282:: with SMTP id j124-v6mr2286936wmg.74.1527854285706; Fri, 01 Jun 2018 04:58:05 -0700 (PDT) Received: from ?IPv6:2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4? ([2a02:c7f:ae6a:ed00:4685:ff:fe66:9f4]) by smtp.gmail.com with ESMTPSA id a14-v6sm759760wmb.44.2018.06.01.04.58.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 04:58:04 -0700 (PDT) Subject: Re: [PATCH] fix build failure with Python 3.7 To: Tom Tromey , Paul.Koning@dell.com Cc: sergiodj@redhat.com, gdb-patches@sourceware.org References: <96198491-96D8-42F0-9956-1C2BC9277050@dell.com> <87fu27fux2.fsf@redhat.com> <2BFDF702-C2E4-4339-ABB4-D0655063DE95@dell.com> <87efhrpa8g.fsf@tromey.com> From: Phil Muldoon Message-ID: Date: Fri, 01 Jun 2018 11:58:00 -0000 MIME-Version: 1.0 In-Reply-To: <87efhrpa8g.fsf@tromey.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00007.txt.bz2 On 01/06/18 02:27, Tom Tromey wrote: >>>>>> writes: > >>> This bug number is actually from Python's bugzilla, not GDB's. So it's >>> not correct to mention it here in the ChangeLog/commit message. AFAIK, >>> there's no correspondent GDB bug filed for this issue. > >> Ok, I removed that. > > There may be other cases where we stick a URL of some non-gdb bug into > the ChangeLog (or at least the commit message), and that seems like it > would save some time for some future archaeologist, so I'd suggest doing > that. > > Tom > Hi all, I think the best thing to do would be to create a GDB bug that then has a reference to the Python bug tracking system. There is a Red Hat bugzilla entry for this, but from an upstream perspective, that's neither here nor there. Cheers, Phil