public inbox for
help / color / mirror / Atom feed
From: Richard Biener <>
Subject: gcc-wwwdocs branch master updated. 6e1dbe9f60b8a49b24d84ed782e8e4ea7b150060
Date: Fri,  1 Oct 2021 07:02:27 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  6e1dbe9f60b8a49b24d84ed782e8e4ea7b150060 (commit)
      from  6fce58b02b953ddcadf9d2f18aa35d8bef69fce5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6e1dbe9f60b8a49b24d84ed782e8e4ea7b150060
Author: Richard Biener <>
Date:   Fri Oct 1 09:01:59 2021 +0200

    Update GCC 12 status, record the start of stage 3

diff --git a/htdocs/develop.html b/htdocs/develop.html
index 5b2a7bf0..4b1f9468 100644
--- a/htdocs/develop.html
+++ b/htdocs/develop.html
@@ -674,6 +674,8 @@ stages of development, branch points, and releases:</p>
        |                                   \
        |                                    v
        |                                   GCC 11.2 release (2021-07-28)
+  GCC 12 Stage 3 (starts 2021-11-15)
+       |
diff --git a/htdocs/index.html b/htdocs/index.html
index 00df1d46..fb0546d2 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -222,7 +222,7 @@ More news? Let know!
   <!--GCC 12 status below-->
-  <a href="">2021-04-20</a>
+  <a href="">2021-10-01</a>
   <!--GCC 12 status above-->
   (general development).
   <div class="regress">


Summary of changes:
 htdocs/develop.html | 2 ++
 htdocs/index.html   | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)


                 reply	other threads:[~2021-10-01  7:02 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).