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. 7a0164f9aa3848bf4cccaccc71f9a7e6bb44a418
Date: Wed, 15 Jul 2020 11:45:56 +0000 (GMT)	[thread overview]
Message-ID: <20200715114556.C788E3851C3E@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  7a0164f9aa3848bf4cccaccc71f9a7e6bb44a418 (commit)
      from  9a6b79af4bedf790f54fb521f063803a1b8351bb (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 7a0164f9aa3848bf4cccaccc71f9a7e6bb44a418
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jul 15 13:45:47 2020 +0200

    update GCC 10 status report link

diff --git a/htdocs/index.html b/htdocs/index.html
index b6b5b6d3..00b34d7c 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -135,7 +135,7 @@ More news? Let gerald@pfeifer.com know!
 </dt><dd>
   Status:
   <!--GCC 10 status below-->
-  <a href="https://gcc.gnu.org/pipermail/gcc/2020-April/000504.html">2020-04-30</a>
+  <a href="https://gcc.gnu.org/pipermail/gcc/2020-July/233135.html">2020-07-15</a>
   <!--GCC 10 status above-->
   (frozen for release).
   <div class="regress">

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

Summary of changes:
 htdocs/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-07-15 11:45 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=20200715114556.C788E3851C3E@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).