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. 9f51d74dc4d2112458e34e06751ac122b0cdb177
Date: Fri, 16 Oct 2020 12:30:55 +0000 (GMT)	[thread overview]
Message-ID: <20201016123055.67D80385702C@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  9f51d74dc4d2112458e34e06751ac122b0cdb177 (commit)
      from  e4d7ebb6579e169f6e17b1fb4b3c315ca6d9b1a0 (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 9f51d74dc4d2112458e34e06751ac122b0cdb177
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Oct 16 14:29:28 2020 +0200

    Update GCC 11 status and timeline
    
    This updates the GCC 11 status report link an the timeline, adding
    the start of stage 3.
    
    2020-10-16  Richard Biener  <rguenther@suse.de>
    
            * develop.html: Add GCC 11 stage 3 start.
            * index.html: Update GCC 11 status report link.

diff --git a/htdocs/develop.html b/htdocs/develop.html
index 46f9becf..e969201d 100644
--- a/htdocs/develop.html
+++ b/htdocs/develop.html
@@ -661,6 +661,8 @@ stages of development, branch points, and releases:</p>
        |                                   \
        |                                    v
        |                                   GCC 10.2 release (2020-06-23)
+  GCC 11 Stage 3 (starts 2020-11-16)
+       |
        v
 </pre>
 
diff --git a/htdocs/index.html b/htdocs/index.html
index d5d1becf..3d129894 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -197,7 +197,7 @@ More news? Let gerald@pfeifer.com know!
 </dt><dd>
   Status:
   <!--GCC 11 status below-->
-  <a href="https://gcc.gnu.org/pipermail/gcc/2020-April/000505.html">2020-04-30</a>
+  <a href="https://gcc.gnu.org/pipermail/gcc/2020-October/234007.html">2020-10-16</a>
   <!--GCC 11 status above-->
   (regression fixes &amp; docs only).
   <div class="regress">

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-10-16 12:30 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=20201016123055.67D80385702C@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).