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. cb7031d6c68e87a39cfdf0d1664c185c87ee734f
Date: Thu, 23 Jul 2020 06:30:36 +0000 (GMT)	[thread overview]
Message-ID: <20200723063036.E7E3D3857C4D@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  cb7031d6c68e87a39cfdf0d1664c185c87ee734f (commit)
      from  bd36510780502458a4dd9696a7a0c3e4786686b0 (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 cb7031d6c68e87a39cfdf0d1664c185c87ee734f
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Jul 23 08:29:53 2020 +0200

    Update gcc-10/ for the GCC 10.2 release

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 2b773f1d..b40f9a57 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -1084,6 +1084,15 @@ known to be fixed in the 10.1 release. This list might not be
 complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
+<!-- .................................................................. -->
+<h2 id="GCC10.2">GCC 10.2</h2>
+
+<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;resolution=FIXED&amp;target_milestone=10.2">list
+of problem reports (PRs)</a> from GCC's bug tracking system that are
+known to be fixed in the 10.2 release. This list might not be
+complete (that is, it is possible that some PRs that have been fixed
+are not listed here).</p>
+
 <!-- .................................................................. -->
 
 </body>
diff --git a/htdocs/gcc-10/index.html b/htdocs/gcc-10/index.html
index 98c10074..f8f8b8b7 100644
--- a/htdocs/gcc-10/index.html
+++ b/htdocs/gcc-10/index.html
@@ -11,18 +11,24 @@
 
 <h1>GCC 10 Release Series</h1>
 
-<p>May 7, 2020</p>
+<p>July 23, 2020</p>
 
 <p>The <a href="http://www.gnu.org">GNU project</a> and the GCC
 developers are pleased to announce the release of GCC 10.1.</p>
 
-<p>This release is a major release, containing new features (as well
-as many other improvements) relative to GCC 9.x.</p>
+<p>This release is a bug-fix release, containing fixes for regressions in
+GCC 10.1 relative to previous releases of GCC.</p>
 
 <h2>Release History</h2>
 
 <dl>
 
+<dt>GCC 10.2</dt>
+<dd>July 23, 2020
+    (<a href="changes.html">changes</a>,
+     <a href="http://gcc.gnu.org/onlinedocs/10.2.0/">documentation</a>)
+</dd>
+
 <dt>GCC 10.1</dt>
 <dd>May 7, 2020
     (<a href="changes.html">changes</a>,

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

Summary of changes:
 htdocs/gcc-10/changes.html |  9 +++++++++
 htdocs/gcc-10/index.html   | 12 +++++++++---
 2 files changed, 18 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-07-23  6: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=20200723063036.E7E3D3857C4D@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).