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. d857139eb40bbda4d056d0afbae61995d9c08bab Date: Wed, 19 Oct 2022 13:17:29 +0000 (GMT) [thread overview] Message-ID: <20221019131729.9282F38515EC@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 d857139eb40bbda4d056d0afbae61995d9c08bab (commit) from bf9d87193528c81b076ff463ff5591e960b6ed63 (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 d857139eb40bbda4d056d0afbae61995d9c08bab Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Oct 19 15:17:15 2022 +0200 Update 10.4.1 Status report. diff --git a/htdocs/index.html b/htdocs/index.html index f9f96607..761a598a 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -228,7 +228,7 @@ More news? Let gerald@pfeifer.com know! </dt><dd> Status: <!--GCC 10 status below--> - <a href="https://gcc.gnu.org/pipermail/gcc/2022-June/238946.html">2022-06-21</a> + <a href="https://gcc.gnu.org/pipermail/gcc/2022-October/239683.html">2022-10-19</a> <!--GCC 10 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-10-19 13: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=20221019131729.9282F38515EC@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).