From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tom@tromey.com>, Paul.Koning@dell.com
Cc: sergiodj@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix build failure with Python 3.7
Date: Fri, 01 Jun 2018 11:58:00 -0000 [thread overview]
Message-ID: <c25f6125-ac2f-c137-29e1-87bb896d109b@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2018-06-01 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96198491-96D8-42F0-9956-1C2BC9277050@dell.com>
2018-05-31 20:45 ` Sergio Durigan Junior
2018-05-31 21:25 ` Paul.Koning
2018-06-01 1:27 ` Tom Tromey
2018-06-01 11:58 ` Phil Muldoon [this message]
[not found] ` <87d0xb34jw.fsf@redhat.com>
2018-06-01 11:56 ` Phil Muldoon
2018-06-01 12:16 ` Pedro Alves
2018-06-01 12:54 ` Paul.Koning
2018-06-01 13:10 ` Pedro Alves
2018-06-01 13:22 ` Paul.Koning
2018-06-01 13:36 ` Pedro Alves
2018-06-01 13:37 ` Pedro Alves
2018-06-01 13:47 ` Paul.Koning
[not found] ` <b1db3ded-7053-3d2b-773e-31ecd20efd90@redhat.com>
2018-06-08 14:37 ` Paul.Koning
2018-06-08 14:55 ` Pedro Alves
2018-06-08 17:36 ` Paul.Koning
2018-06-09 0:26 ` Sergio Durigan Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c25f6125-ac2f-c137-29e1-87bb896d109b@redhat.com \
--to=pmuldoon@redhat.com \
--cc=Paul.Koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox