public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 069771d26d1384ec482fe27ff21d5cb43d3948ad
Date: Mon,  8 May 2023 12:15:26 +0000 (GMT)	[thread overview]
Message-ID: <20230508121526.9716E385840C@sourceware.org> (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  069771d26d1384ec482fe27ff21d5cb43d3948ad (commit)
      from  4da64180a139c25d9da85342fcbae5fef0de3b8c (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 069771d26d1384ec482fe27ff21d5cb43d3948ad
Author: Richard Biener <rguenther@suse.de>
Date:   Mon May 8 14:15:07 2023 +0200

    Release preps
    C

diff --git a/htdocs/develop.html b/htdocs/develop.html
index 564b2cbe..e7854ec3 100644
--- a/htdocs/develop.html
+++ b/htdocs/develop.html
@@ -693,9 +693,9 @@ stages of development, branch points, and releases:</p>
        |                                   \
        |                                    v
        |                                   GCC 12.2 release (2022-08-19)
-  GCC 13 Stage 3 (starts 2022-11-14)
-       |
-  GCC 13 Stage 4 (starts 2023-01-16)
+  GCC 13 Stage 3 (starts 2022-11-14)         \
+       |                                      v
+  GCC 13 Stage 4 (starts 2023-01-16)       GCC 12.3 release (2023-05-08)
        |
        +-- GCC 13 branch created -------+
        |                                 \
diff --git a/htdocs/gcc-12/index.html b/htdocs/gcc-12/index.html
index 503bedd3..f8c589e8 100644
--- a/htdocs/gcc-12/index.html
+++ b/htdocs/gcc-12/index.html
@@ -11,7 +11,7 @@
 
 <h1>GCC 12 Release Series</h1>
 
-<p>May 5, 2023</p>
+<p>May 8, 2023</p>
 
 <p>The GCC developers are pleased to announce the release of GCC 12.3.</p>
 
@@ -23,7 +23,7 @@ GCC 12.2 relative to previous releases of GCC.</p>
 <dl>
 
 <dt>GCC 12.3</dt>
-<dd>May 5, 2023
+<dd>May 8, 2023
     (<a href="changes.html">changes</a>,
      <a href="http://gcc.gnu.org/onlinedocs/12.3.0/">documentation</a>)
 </dd>
diff --git a/htdocs/releases.html b/htdocs/releases.html
index dc0d77ab..0bf6c9e5 100644
--- a/htdocs/releases.html
+++ b/htdocs/releases.html
@@ -33,6 +33,7 @@ releases and an alternative view of the release history.</p>
 
 <table class="padding5">
 <tr><th>Release</th><th>Release date</th></tr>
+<tr><td><a href="gcc-12/">GCC 12.3</a></td>     <td>May 8, 2023</td></tr>
 <tr><td><a href="gcc-13/">GCC 13.1</a></td>     <td>April 26, 2023</td></tr>
 <tr><td><a href="gcc-12/">GCC 12.2</a></td>     <td>August 19, 2022</td></tr>
 <tr><td><a href="gcc-10/">GCC 10.4</a></td>     <td>June 28, 2022</td></tr>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/develop.html      | 6 +++---
 htdocs/gcc-12/index.html | 4 ++--
 htdocs/releases.html     | 1 +
 3 files changed, 6 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-05-08 12:15 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=20230508121526.9716E385840C@sourceware.org \
    --to=rguenth@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).