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. 8fb92c2b989db3d72bb2b8db41b3231b5497e678 Date: Fri, 27 Jan 2023 00:13:47 +0000 (GMT) [thread overview] Message-ID: <20230127001347.9DBE33858D20@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 8fb92c2b989db3d72bb2b8db41b3231b5497e678 (commit) from 4d66c39fd9829e03ebc707ed7d9e82be18b450e4 (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 8fb92c2b989db3d72bb2b8db41b3231b5497e678 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Jan 27 01:09:04 2023 +0100 codingconventions: Update upstream instructions for libstdc++ Since ca314fbd2509439f708c56f34d0a85449a43fe73 in the gcc tree libstc++ no longer ships copies of files from the C++ committee homepage. Simplify instructions how to sync from upstream accordingly. diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index 5519d3f9..af08f11a 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -756,8 +756,7 @@ first. </li> <li>libstdc++-v3: In docs/doxygen, comments in *.cfg.in are partially autogenerated from <a href="https://www.doxygen.nl">the -Doxygen tool</a>. In docs/html, the ext/lwg-* files are copied from <a -href="http://www.open-std.org/jtc1/sc22/wg21/">the C++ committee homepage</a>, +Doxygen tool</a>. In docs/html, the 27_io/binary_iostream_* files are copies of Usenet postings, and most of the files in 17_intro are either copied from elsewhere in GCC or the FSF website, or are autogenerated. These files should not be changed ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-27 0:13 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=20230127001347.9DBE33858D20@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).