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. 160086f72bf574ebb7992218c8759be83c521e98
Date: Wed, 27 Jul 2022 10:20:29 +0000 (GMT) [thread overview]
Message-ID: <20220727102029.274B53857001@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 160086f72bf574ebb7992218c8759be83c521e98 (commit)
from b5a9a68ce410f0f420be261e5266c1e64071baae (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 160086f72bf574ebb7992218c8759be83c521e98
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jul 27 12:20:16 2022 +0200
Update gcc 12 status report link
diff --git a/htdocs/index.html b/htdocs/index.html
index e63e4f1a..76acc7e0 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -184,7 +184,7 @@ More news? Let gerald@pfeifer.com know!
</dt><dd>
Status:
<!--GCC 12 status below-->
- <a href="https://gcc.gnu.org/pipermail/gcc/2022-May/238654.html">2022-05-06</a>
+ <a href="https://gcc.gnu.org/pipermail/gcc/2022-July/239190.html">2022-07-27</a>
<!--GCC 12 status above-->
(regression fixes & 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:[~2022-07-27 10:20 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=20220727102029.274B53857001@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).