From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 13.2.1 Status Report (2023-07-27)
Date: Thu, 27 Jul 2023 14:10:19 +0200 [thread overview]
Message-ID: <ZMJeq/Y5SN+7i8a+@tucnak> (raw)
Status
======
GCC 13.2 has been released, the releases/gcc-13 branch is open again
for regression and documentation bugfixing. GCC 13.3 can be expected
in spring next year unless something serious changes the plans.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0
P2 512 + 1
P3 126 + 6
P4 214
P5 24
-------- --- -----------------------
Total P1-P3 638 + 7
Total 876 + 7
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2023-July/242117.html
reply other threads:[~2023-07-27 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZMJeq/Y5SN+7i8a+@tucnak \
--to=jakub@redhat.com \
--cc=gcc@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).