This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] fix build failure with Python 3.7
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Tom Tromey <tom at tromey dot com>, Paul dot Koning at dell dot com
- Cc: sergiodj at redhat dot com, gdb-patches at sourceware dot org
- Date: Fri, 1 Jun 2018 12:58:04 +0100
- Subject: Re: [PATCH] fix build failure with Python 3.7
- References: <96198491-96D8-42F0-9956-1C2BC9277050@dell.com> <87fu27fux2.fsf@redhat.com> <2BFDF702-C2E4-4339-ABB4-D0655063DE95@dell.com> <87efhrpa8g.fsf@tromey.com>
On 01/06/18 02:27, Tom Tromey wrote:
>>>>>> <Paul.Koning@dell.com> 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