public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: rguenth@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d08cae0347fc93096499c91de0e053c3ebc7c614
Date: Thu, 14 Nov 2019 07:35:00 -0000	[thread overview]
Message-ID: <20191114073539.124002.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  d08cae0347fc93096499c91de0e053c3ebc7c614 (commit)
      from  f5b29a8fdedd895613f7304227d877d5add1535d (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 d08cae0347fc93096499c91de0e053c3ebc7c614
Author: Richard Guenther <rguenther@suse.de>
Date:   Thu Nov 14 08:35:11 2019 +0100

    2019-11-14  Richard Biener  <rguenther@suse.de>
    
    	* gcc-7/changes.html: Add 7.5 subsection.
    	* gcc-7/index.html: Add 7.5 release.

diff --git a/htdocs/gcc-7/changes.html b/htdocs/gcc-7/changes.html
index adb69ed..3a14c5c 100644
--- a/htdocs/gcc-7/changes.html
+++ b/htdocs/gcc-7/changes.html
@@ -1350,6 +1350,16 @@ complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
 <!-- .................................................................. -->
+<h2 id="GCC7.5">GCC 7.5</h2>
+
+<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;resolution=FIXED&amp;target_milestone=7.5">list
+of problem reports (PRs)</a> from GCC's bug tracking system that are
+known to be fixed in the 7.5 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-7/index.html b/htdocs/gcc-7/index.html
index 1da10d7..3d074f5 100644
--- a/htdocs/gcc-7/index.html
+++ b/htdocs/gcc-7/index.html
@@ -10,18 +10,24 @@
 
 <h1>GCC 7 Release Series</h1>
 
-<p>Dec 6, 2018</p>
+<p>Nov 14, 2019</p>
 
 <p>The <a href="http://www.gnu.org">GNU project</a> and the GCC
-developers are pleased to announce the release of GCC 7.4.</p>
+developers are pleased to announce the release of GCC 7.5.</p>
 
 <p>This release is a bug-fix release, containing fixes for regressions in
-GCC 7.3 relative to previous releases of GCC.</p>
+GCC 7.4 relative to previous releases of GCC.</p>
 
 <h2>Release History</h2>
 
 <dl>
 
+<dt>GCC 7.5</dt>
+<dd>Nov 14, 2019
+    (<a href="changes.html">changes</a>,
+     <a href="http://gcc.gnu.org/onlinedocs/7.5.0/">documentation</a>)
+</dd>
+
 <dt>GCC 7.4</dt>
 <dd>Dec 6, 2018
     (<a href="changes.html">changes</a>,

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2019-11-14  7:35 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=20191114073539.124002.qmail@sourceware.org \
    --to=rguenth@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: 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).