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. 8e5b3570e9eb9bd88e810d0d9670199078b685d4 Date: Fri, 6 May 2022 09:50:35 +0000 (GMT) [thread overview] Message-ID: <20220506095035.9593F394D83B@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 8e5b3570e9eb9bd88e810d0d9670199078b685d4 (commit) from b000efb45e7fb5f263619d83e34c23c64ef64f37 (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 8e5b3570e9eb9bd88e810d0d9670199078b685d4 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri May 6 11:50:24 2022 +0200 Update 12.1.1 Status report. diff --git a/htdocs/index.html b/htdocs/index.html index 7eaf913b..a30872fc 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -176,7 +176,7 @@ More news? Let gerald@pfeifer.com know! </dt><dd> Status: <!--GCC 12 status below--> - <a href="https://gcc.gnu.org/pipermail/gcc/2022-April/238617.html">2022-04-28</a> + <a href="https://gcc.gnu.org/pipermail/gcc/2022-May/238654.html">2022-05-06</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-05-06 9:50 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=20220506095035.9593F394D83B@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).