From: Richard Biener <rguenther@suse.de>
To: Andreas Krebbel <krebbel@linux.ibm.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 11.2.1 Status Report (2022-04-13), branch frozen for release
Date: Thu, 14 Apr 2022 10:02:46 +0200 (CEST) [thread overview]
Message-ID: <983s6q46-p438-s446-37nn-5n5qs67s4s7r@fhfr.qr> (raw)
In-Reply-To: <b30f60cf-300f-7f38-1a51-fefdd2220e40@linux.ibm.com>
On Thu, 14 Apr 2022, Andreas Krebbel wrote:
> On 4/13/22 09:30, Richard Biener via Gcc wrote:
> >
> > Status
> > ======
> >
> > The gcc-11 branch is now frozen in preparation for a GCC 11.3 release
> > candidate and the GCC 11.3 release next week. All changes now require
> > release manager approval.
>
> Hi,
>
> I would like to push:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593103.html
>
> to GCC 11 branch before 11.3 release. Ok?
OK.
Richard.
prev parent reply other threads:[~2022-04-14 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:30 Richard Biener
2022-04-14 7:11 ` Andreas Krebbel
2022-04-14 8:02 ` Richard Biener [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=983s6q46-p438-s446-37nn-5n5qs67s4s7r@fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=krebbel@linux.ibm.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).