public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 47984503327ac5338067f7637d67641478e08e5e Date: Thu, 10 Nov 2022 08:07:28 +0000 (GMT) [thread overview] Message-ID: <20221110080728.A2D7F3858D28@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 47984503327ac5338067f7637d67641478e08e5e (commit) from e8afc930bc6cd9057c27b0752061ba478c692f80 (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 47984503327ac5338067f7637d67641478e08e5e Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Nov 10 09:07:01 2022 +0100 c99status: Switch www.open-std.org to https diff --git a/htdocs/c99status.html b/htdocs/c99status.html index 615394f4..85adb158 100644 --- a/htdocs/c99status.html +++ b/htdocs/c99status.html @@ -19,7 +19,7 @@ Annexes F and G). The following table gives more details of the C99 support in different GCC versions.</p> <p>This table is based on the list in the foreword to <a -href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf">N1256</a> +href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf">N1256</a> (ISO/IEC 9899:1999 (E), consolidated with ISO/IEC 9899:1999/Cor.1:2001 (E), ISO/IEC 9899:1999/Cor.2:2004 (E) and ISO/IEC 9899:1999/Cor.3:2007 (E)).</p> ----------------------------------------------------------------------- Summary of changes: htdocs/c99status.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-10 8:07 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=20221110080728.A2D7F3858D28@sourceware.org \ --to=gerald@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).