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. c64a22493359c02392aed483d514c6d3a28832c4
Date: Mon, 17 Apr 2023 11:03:33 +0000 (GMT)	[thread overview]
Message-ID: <20230417110333.08D7B3856DCD@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  c64a22493359c02392aed483d514c6d3a28832c4 (commit)
      from  8137d37b26794c5bcad139423abddcd105a33780 (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 c64a22493359c02392aed483d514c6d3a28832c4
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Apr 17 13:02:27 2023 +0200

    Update GCC 12 status report link

diff --git a/htdocs/index.html b/htdocs/index.html
index 27f8272b..f75c916d 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -110,7 +110,7 @@ More news? Let gerald@pfeifer.com know!
 </dt><dd>
   Status:
   <!--GCC 12 status below-->
-  <a href="https://gcc.gnu.org/pipermail/gcc/2022-August/239300.html">2022-08-19</a>
+  <a href="https://gcc.gnu.org/pipermail/gcc/2023-April/241138.html">2023-04-17</a>
   <!--GCC 12 status above-->
   (regression fixes &amp; docs only).
   <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:[~2023-04-17 11:03 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=20230417110333.08D7B3856DCD@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).