public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. c26e5e066e599e56dcf3ae0d283e71b548bc3e06 Date: Wed, 04 Mar 2020 08:25:00 -0000 [thread overview] Message-ID: <20200304082517.13751.qmail@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 c26e5e066e599e56dcf3ae0d283e71b548bc3e06 (commit) from 6b92a4c7033db33ed5b6827e826a561077ed2181 (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 c26e5e066e599e56dcf3ae0d283e71b548bc3e06 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Mar 4 09:25:07 2020 +0100 Preparing 8.4 release. diff --git a/htdocs/gcc-8/changes.html b/htdocs/gcc-8/changes.html index 636552ab..83dd1bc0 100644 --- a/htdocs/gcc-8/changes.html +++ b/htdocs/gcc-8/changes.html @@ -1385,5 +1385,14 @@ are not listed here).</p> cases of this defect in single change. </ul> +<!-- .................................................................. --> +<h2 id="GCC8.4">GCC 8.4</h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=8.4">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 8.4 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> </html> diff --git a/htdocs/gcc-8/index.html b/htdocs/gcc-8/index.html index ab9a865c..4d7541a8 100644 --- a/htdocs/gcc-8/index.html +++ b/htdocs/gcc-8/index.html @@ -11,18 +11,24 @@ <h1>GCC 8 Release Series</h1> -<p>Feb 22, 2019</p> +<p>Mar 4, 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 8.3.</p> +developers are pleased to announce the release of GCC 8.4.</p> <p>This release is a bug-fix release, containing fixes for regressions in -GCC 8.2 relative to previous releases of GCC.</p> +GCC 8.3 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 8.4</dt> +<dd>Mar 4, 2020 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/8.4.0/">documentation</a>) +</dd> + <dt>GCC 8.3</dt> <dd>Feb 22, 2019 (<a href="changes.html">changes</a>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-8/changes.html | 9 +++++++++ htdocs/gcc-8/index.html | 12 +++++++++--- 2 files changed, 18 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-03-04 8:25 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=20200304082517.13751.qmail@sourceware.org \ --to=jakub@gcc.gnu.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).