public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathaniel Shead <nathanieloshead@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [Ping][PATCH] libstdc++: Add missing functions to <cmath> [PR79700]
Date: Wed, 17 May 2023 18:37:16 +1000	[thread overview]
Message-ID: <CACEF2k4Cy6=u+83YdzwPCC0ecYWugb3qNAC2tEi5VAWHcgGeCA@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4=-XZtGHa3H-AkR9TzaB-vjnKn9X6Z1C4PdyScc361R4A@mail.gmail.com>

Now that GCC13.1 is released is it ok to merge? Thanks!

On Tue, Apr 18, 2023 at 6:48 PM Jonathan Wakely <jwakely@redhat.com> wrote:
>
> On Mon, 17 Apr 2023 at 09:11, Nathaniel Shead <nathanieloshead@gmail.com> wrote:
> >
> > Hi, just checking whether there were any issues with this patch?
> > https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612386.html
> >
> > Otherwise I assume it won't be in GCC13.
>
> That's right, it's too large and invasive a change to get into GCC 13
> when only submitted in February, sorry. I'll merge it to trunk once
> GCC 13.1 is released though.
>

  reply	other threads:[~2023-05-17  8:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 11:23 [PATCH] " Nathaniel Shead
2023-02-20 11:30 ` Jonathan Wakely
2023-02-20 11:57   ` Nathaniel Shead
2023-02-20 12:08     ` Jonathan Wakely
2023-02-21 11:22       ` Nathaniel Shead
2023-04-17  8:10         ` [Ping][PATCH] " Nathaniel Shead
2023-04-18  8:47           ` Jonathan Wakely
2023-05-17  8:37             ` Nathaniel Shead [this message]
2023-05-17  9:05               ` Jonathan Wakely
2023-05-17  9:38                 ` Nathaniel Shead
2023-05-17 10:07                   ` Jonathan Wakely
2023-11-11  0:43                     ` Jonathan Wakely

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='CACEF2k4Cy6=u+83YdzwPCC0ecYWugb3qNAC2tEi5VAWHcgGeCA@mail.gmail.com' \
    --to=nathanieloshead@gmail.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).