From: Jonathan Yong <10walls@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: PING^1 [PATCH] testsuite: Windows reports errors with CreateProcess
Date: Wed, 5 Oct 2022 09:48:59 +0000 [thread overview]
Message-ID: <80525a39-f742-9c79-17b1-9ac99b7f5e9c@gmail.com> (raw)
In-Reply-To: <0e9221ed-9709-9dc5-532d-d4f637314dfb@foss.st.com>
On 10/5/22 09:15, Torbjorn SVENSSON via Gcc-patches wrote:
> Hi,
>
> Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602541.html
>
> Kind regards,
> Torbjörn
>
Looks good to me, pushed to master branch as
fa8e3a055a082e38aeab2561a5016b01ebfd6ebd.
prev parent reply other threads:[~2022-10-05 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 18:07 Torbjörn SVENSSON
2022-10-05 9:15 ` PING^1 " Torbjorn SVENSSON
2022-10-05 9:48 ` 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=80525a39-f742-9c79-17b1-9ac99b7f5e9c@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@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).