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. be4eb2943b6eb2949b2a3363f47fb545d3807f04 Date: Wed, 28 Jul 2021 06:52:30 +0000 (GMT) [thread overview] Message-ID: <20210728065230.298EA382C421@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 be4eb2943b6eb2949b2a3363f47fb545d3807f04 (commit) from 0e4db42cddd88d2cc6780da884021284a10b9a4b (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 be4eb2943b6eb2949b2a3363f47fb545d3807f04 Author: Richard Biener <rguenther@suse.de> Date: Wed Jul 28 08:52:12 2021 +0200 gcc-11/ updates for the GCC 11.2 release diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 491b6b71..b8bb2e69 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -1105,6 +1105,15 @@ known to be fixed in the 11.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><a name="11.2">GCC 11.2</a></h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.2">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 11.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-11/index.html b/htdocs/gcc-11/index.html index cc64e2b7..56c2ab5b 100644 --- a/htdocs/gcc-11/index.html +++ b/htdocs/gcc-11/index.html @@ -11,17 +11,23 @@ <h1>GCC 11 Release Series</h1> -<p>April 27, 2021</p> +<p>July 28, 2021</p> -<p>The GCC developers are pleased to announce the release of GCC 11.1.</p> +<p>The GCC developers are pleased to announce the release of GCC 11.2.</p> -<p>This release is a major release, containing new features (as well -as many other improvements) relative to GCC 10.x.</p> +<p>This release is a bug-fix release, containing fixes for regressions in +GCC 11.1 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 11.2</dt> +<dd>July 28, 2021 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/11.2.0/">documentation</a>) +</dd> + <dt>GCC 11.1</dt> <dd>April 27, 2021 (<a href="changes.html">changes</a>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 9 +++++++++ htdocs/gcc-11/index.html | 14 ++++++++++---- 2 files changed, 19 insertions(+), 4 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-07-28 6:52 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=20210728065230.298EA382C421@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: linkBe 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).