public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 09f0f3883e1c68af7aca867b15ae5fcc39bdd6ae Date: Fri, 7 May 2021 19:56:07 +0000 (GMT) [thread overview] Message-ID: <20210507195607.8AF603A3E035@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 09f0f3883e1c68af7aca867b15ae5fcc39bdd6ae (commit) from 9a0dc724500db0e43d86e0c016e8a5eef572a30b (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 09f0f3883e1c68af7aca867b15ae5fcc39bdd6ae Author: Jakub Jelinek <jakub@redhat.com> Date: Fri May 7 21:55:47 2021 +0200 Update 8.5 status report URL and mention it is frozen. diff --git a/htdocs/index.html b/htdocs/index.html index d01596ad..22b35a42 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -205,9 +205,9 @@ More news? Let gerald@pfeifer.com know! </dt><dd> Status: <!--GCC 8 status below--> - <a href="https://gcc.gnu.org/pipermail/gcc/2021-April/235871.html">2021-04-23</a> + <a href="https://gcc.gnu.org/pipermail/gcc/2021-May/235996.html">2021-05-07</a> <!--GCC 8 status above--> - (regression fixes & docs only). + (frozen for release). <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)*8%5B%20%2F%5D%5B%200-9.%2F%5D*%5BRr%5Degression%20*%5C%5D&target_milestone=8.5&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:[~2021-05-07 19:56 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=20210507195607.8AF603A3E035@sourceware.org \ --to=jakub@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: linkBe 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).