From: Ben Boeckel <ben.boeckel@kitware.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org, nathan@acm.org, fortran@gcc.gnu.org,
gcc@gcc.gnu.org, brad.king@kitware.com
Subject: Re: [PATCH v8 0/4] P1689R5 support
Date: Wed, 20 Sep 2023 10:44:42 -0400 [thread overview]
Message-ID: <ZQsFWikMppRx+Y6b@farprobe> (raw)
In-Reply-To: <99ce75f4-a654-581c-30f7-7fce16b8106e@redhat.com>
On Tue, Sep 19, 2023 at 17:33:34 -0400, Jason Merrill wrote:
> Pushed, thanks!
Thanks!
Is there a process I can use to backport this to GCC 13?
--Ben
prev parent reply other threads:[~2023-09-20 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 13:04 Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 1/4] spec: add a spec function to join arguments Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 2/4] p1689r5: initial support Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 3/4] c++modules: report imported CMI files as dependencies Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 4/4] c++modules: report module mapper files as a dependency Ben Boeckel
2023-09-19 21:33 ` [PATCH v8 0/4] P1689R5 support Jason Merrill
2023-09-20 14:44 ` Ben Boeckel [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=ZQsFWikMppRx+Y6b@farprobe \
--to=ben.boeckel@kitware.com \
--cc=brad.king@kitware.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.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).