From: Jonathan Wakely <jwakely@redhat.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] Relax type-printer regexp in libstdc++ test suite
Date: Thu, 29 Jun 2023 19:00:47 +0100 [thread overview]
Message-ID: <CACb0b4nTDhQC0iVySR_QH-nzxr4iyGc8aUnKBdRCKfNeA1UxyA@mail.gmail.com> (raw)
In-Reply-To: <87pm5ew6gc.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Thu, 29 Jun 2023 at 17:59, Tom Tromey <tromey@adacore.com> wrote:
> >>>>> Jonathan Wakely <jwakely@redhat.com> writes:
>
> > Looks good. OK for trunk, and OK to backport after some soak time on
> trunk. Thanks.
>
> AdaCore doesn't need a backport of this, and I don't think it's
> extremely important; so unless you want me to do it, I don't plan to.
>
OK, we can always backport it later if anybody else needs it.
> I did check it in on trunk earlier today.
>
>
Thanks.
prev parent reply other threads:[~2023-06-29 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 15:57 Tom Tromey
2023-06-28 18:05 ` Jonathan Wakely
2023-06-29 16:58 ` Tom Tromey
2023-06-29 18:00 ` Jonathan Wakely [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=CACb0b4nTDhQC0iVySR_QH-nzxr4iyGc8aUnKBdRCKfNeA1UxyA@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=tromey@adacore.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).