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. 4295a5d589cab19d8935c01e9993c25a50d48adb
Date: Mon, 20 Nov 2023 08:17:17 +0000 (GMT) [thread overview]
Message-ID: <20231120081717.CB90D38618A0@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 4295a5d589cab19d8935c01e9993c25a50d48adb (commit)
via 5c543b12ae6824cd06ef779949717599768647ca (commit)
from d74e228b079673bee7a601ffd341c923e7d4916f (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 4295a5d589cab19d8935c01e9993c25a50d48adb
Author: Richard Biener <rguenther@suse.de>
Date: Mon Nov 20 09:13:14 2023 +0100
Update GCC 14 status report link
diff --git a/htdocs/index.html b/htdocs/index.html
index cb47598a..feecf37a 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -191,7 +191,7 @@ More news? Let gerald@pfeifer.com know!
</dt><dd>
Status:
<!--GCC 14 status below-->
- <a href="https://gcc.gnu.org/pipermail/gcc/2023-October/242733.html">2023-10-18</a>
+ <a href="https://gcc.gnu.org/pipermail/gcc/2023-November/242898.html">2023-11-20</a>
<!--GCC 14 status above-->
(general bugfixing).
<div class="regress">
commit 5c543b12ae6824cd06ef779949717599768647ca
Author: Richard Biener <rguenther@suse.de>
Date: Mon Nov 20 09:06:50 2023 +0100
Mark trunk as in stage3
diff --git a/htdocs/index.html b/htdocs/index.html
index c87292a5..cb47598a 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -193,7 +193,7 @@ More news? Let gerald@pfeifer.com know!
<!--GCC 14 status below-->
<a href="https://gcc.gnu.org/pipermail/gcc/2023-October/242733.html">2023-10-18</a>
<!--GCC 14 status above-->
- (general development).
+ (general bugfixing).
<div class="regress">
<a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=regexp&short_desc=%5C%5B(%5B%200-9.%2F%5D*%5B%20%2F%5D)*14%5B%20%2F%5D%5B%200-9.%2F%5D*%5BRr%5Degression%20*%5C%5D&target_milestone=11.5&target_milestone=12.4&target_milestone=13.3&target_milestone=14.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Serious
-----------------------------------------------------------------------
Summary of changes:
htdocs/index.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2023-11-20 8:17 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=20231120081717.CB90D38618A0@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).