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. f035e253aff937bbb12467b5d383cfbde5a31815
Date: Mon, 14 Nov 2022 13:23:04 +0000 (GMT) [thread overview]
Message-ID: <20221114132304.4845A383569C@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 f035e253aff937bbb12467b5d383cfbde5a31815 (commit)
from 6e41ef3dbbc0e2a774e3fd0947857c75e0d16da2 (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 f035e253aff937bbb12467b5d383cfbde5a31815
Author: Richard Biener <rguenther@suse.de>
Date: Mon Nov 14 14:22:54 2022 +0100
Update GCC 13 status report
diff --git a/htdocs/index.html b/htdocs/index.html
index decd4ff6..655b7373 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -178,9 +178,9 @@ More news? Let gerald@pfeifer.com know!
</dt><dd>
Status:
<!--GCC 13 status below-->
- <a href="https://gcc.gnu.org/pipermail/gcc/2022-October/239690.html">2022-10-20</a>
+ <a href="https://gcc.gnu.org/pipermail/gcc/2022-November/239994.html">2022-11-14</a>
<!--GCC 13 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)*13%5B%20%2F%5D%5B%200-9.%2F%5D*%5BRr%5Degression%20*%5C%5D&target_milestone=10.5&target_milestone=11.4&target_milestone=12.3&target_milestone=13.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:[~2022-11-14 13:23 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=20221114132304.4845A383569C@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).