From: "Hoyer, David" <David.Hoyer@netapp.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: printers.py issue
Date: Thu, 11 Mar 2021 18:33:37 +0000 [thread overview]
Message-ID: <DM5PR06MB2809DCF2FC996B0F7605BAEE92909@DM5PR06MB2809.namprd06.prod.outlook.com> (raw)
In-Reply-To: <20210311175628.GF3008@redhat.com>
Thank you so much for taking the time to help me with this! It was greatly appreciated.
-----Original Message-----
From: Jonathan Wakely <jwakely@redhat.com>
Sent: Thursday, March 11, 2021 11:56 AM
To: Hoyer, David <David.Hoyer@netapp.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>; gcc-patches@gcc.gnu.org
Subject: Re: printers.py issue
NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 10/03/21 16:57 +0000, Hoyer, David wrote:
>I wanted to finally follow up on these issues I reported.
>
>On issue 1, the patch you provided did fix the problem
Thanks for confirming. It's committed to the master branch now (as attached to this mail). I also plan to backport it to the active release branches later.
>On issue 2, I changed our python script to convert it to a string and it now works!
Great. I think it's correct that those constructor methods expect strings for the 'typename' parameter.
prev parent reply other threads:[~2021-03-11 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR06MB28097C4E645110031875A391929D9@DM5PR06MB2809.namprd06.prod.outlook.com>
2021-02-26 22:27 ` Jonathan Wakely
2021-02-26 22:31 ` Hoyer, David
2021-03-04 4:35 ` Hoyer, David
2021-03-04 11:47 ` Jonathan Wakely
2021-03-04 14:19 ` Hoyer, David
2021-03-04 14:57 ` Jonathan Wakely
2021-03-10 16:57 ` Hoyer, David
2021-03-11 17:56 ` Jonathan Wakely
2021-03-11 18:33 ` Hoyer, David [this message]
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=DM5PR06MB2809DCF2FC996B0F7605BAEE92909@DM5PR06MB2809.namprd06.prod.outlook.com \
--to=david.hoyer@netapp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
/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).