From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: C++ Patch ping^2
Date: Wed, 10 Apr 2024 13:02:30 +0200 [thread overview]
Message-ID: <ZhZxxvqaLY2xchTw@tucnak> (raw)
In-Reply-To: <Zg0l5JMkcOb5KVz2@tucnak>
Hi!
On Wed, Apr 03, 2024 at 11:48:20AM +0200, Jakub Jelinek wrote:
> I'd like to ping the following patches:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647445.html
> PR111284 P2
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-March/648215.html
> PR114409 (part of a P1)
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-March/648381.html
> PR114426 P1
Thanks
Jakub
next prev parent reply other threads:[~2024-04-10 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:48 C++ Patch ping Jakub Jelinek
2024-04-10 11:02 ` Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 13:56 C++ patch ping^2 Jakub Jelinek
2020-11-18 9:38 Jakub Jelinek
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=ZhZxxvqaLY2xchTw@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@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).