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. 0f14b833324cb74279632a8e9904311d9ddd6cc4 Date: Tue, 31 Jan 2023 00:38:36 +0000 (GMT) [thread overview] Message-ID: <20230131003836.2CFB43858D1E@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 0f14b833324cb74279632a8e9904311d9ddd6cc4 (commit) from 53d4c04b3a82673f6ed3a9c419fd379d1fc09685 (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 0f14b833324cb74279632a8e9904311d9ddd6cc4 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Jan 31 01:37:56 2023 +0100 cxx-dr-status: Switch www.open-std.org to https diff --git a/htdocs/projects/cxx-dr-status.html b/htdocs/projects/cxx-dr-status.html index 748226c2..d87466a3 100644 --- a/htdocs/projects/cxx-dr-status.html +++ b/htdocs/projects/cxx-dr-status.html @@ -15,7 +15,7 @@ <p>This table tracks the implementation status of C++ defect reports in GCC. It is based on C++ Standard Core Language Issue Table of Contents, Revision - 109 (<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_toc.html">here</a>).</p> + 109 (<a href="https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_toc.html">here</a>).</p> <table class="cxxdrstatus" style="width: 66.6%"> <tr class="separator"> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cxx-dr-status.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-31 0:38 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=20230131003836.2CFB43858D1E@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).