From: <Paul.Koning@dell.com>
To: <palves@redhat.com>
Cc: <sergiodj@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fix build failure with Python 3.7
Date: Fri, 01 Jun 2018 13:47:00 -0000 [thread overview]
Message-ID: <E6C83A58-BCBE-41FA-B360-EE27C7EF6B3E@dell.com> (raw)
In-Reply-To: <fa0b71d9-e2cc-294e-0895-b33eef2dd885@redhat.com>
> On Jun 1, 2018, at 9:37 AM, Pedro Alves <palves@redhat.com> wrote:
>
> 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?
>>
>> Yes, but recall to include the rationale in the git commit log, and
>> to include the link to the original Python issue in there.
>
> 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=23252
paul
next prev parent reply other threads:[~2018-06-01 13:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 18:20 Paul.Koning
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
[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 [this message]
2018-06-08 14:35 ` Pedro Alves
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=E6C83A58-BCBE-41FA-B360-EE27C7EF6B3E@dell.com \
--to=paul.koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).