public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 9e3d870b7824d883282a5bf1cc49d6626d28b2ac Date: Thu, 12 Mar 2020 11:04:16 +0000 (GMT) [thread overview] Message-ID: <20200312110416.2A39A3944428@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 9e3d870b7824d883282a5bf1cc49d6626d28b2ac (commit) from f92260c29a59728f1a5837fe10df7f75ed378cd1 (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 9e3d870b7824d883282a5bf1cc49d6626d28b2ac Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Mar 12 12:03:54 2020 +0100 Preparing 9.3 release. diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html index 22b069c5..d5469ec4 100644 --- a/htdocs/gcc-9/changes.html +++ b/htdocs/gcc-9/changes.html @@ -1122,6 +1122,15 @@ known to be fixed in the 9.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> +<!-- .................................................................. --> +<h2 id="GCC9.3">GCC 9.3</h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=9.3">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 9.3 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-9/index.html b/htdocs/gcc-9/index.html index da01f2f2..4ca779c8 100644 --- a/htdocs/gcc-9/index.html +++ b/htdocs/gcc-9/index.html @@ -11,18 +11,24 @@ <h1>GCC 9 Release Series</h1> -<p>Aug 12, 2019</p> +<p>Mar 12, 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 9.2.</p> +developers are pleased to announce the release of GCC 9.3.</p> <p>This release is a bug-fix release, containing fixes for regressions in -GCC 9.1 relative to previous releases of GCC.</p> +GCC 9.2 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 9.3</dt> +<dd>Mar 12, 2020 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/9.3.0/">documentation</a>) +</dd> + <dt>GCC 9.2</dt> <dd>Aug 12, 2019 (<a href="changes.html">changes</a>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-9/changes.html | 9 +++++++++ htdocs/gcc-9/index.html | 12 +++++++++--- 2 files changed, 18 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-03-12 11:04 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=20200312110416.2A39A3944428@sourceware.org \ --to=jakub@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).