From: Jonathan Yong <10walls@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Eric Botcazou <botcazou@adacore.com>
Subject: Re: [PATCH] libstdc++: Fix unintended layout change to std::basic_filebuf [PR108331]
Date: Fri, 13 Jan 2023 00:45:04 +0000 [thread overview]
Message-ID: <ad8d4946-a695-d02c-fe8a-f37eb6a00eb7@gmail.com> (raw)
In-Reply-To: <20230112211010.932966-1-jwakely@redhat.com>
On 1/12/23 21:10, Jonathan Wakely wrote:
> Tested x86_64-linux. Bootstrapped x86_64-w64-mingw32 with both
> --enable-threads=posix and --enable-threads=win32.
>
> I need a libgcc or mingw maintainer to approve the gthr-win32.h part.
>
> OK for trunk?
>
Looks good to me even if its a dummy member. Thanks for the patch.
prev parent reply other threads:[~2023-01-13 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:10 Jonathan Wakely
2023-01-13 0:45 ` Jonathan Yong [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=ad8d4946-a695-d02c-fe8a-f37eb6a00eb7@gmail.com \
--to=10walls@gmail.com \
--cc=botcazou@adacore.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).