From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++
Date: Fri, 27 Jan 2023 01:16:15 +0100 (CET) [thread overview]
Message-ID: <20230127001617.CE64D33E9E@hamza.pair.com> (raw)
Jonathan (or some other libstdc++ developer), would you mind having a
look at that section of https://gcc.gnu.org/codingconventions.html to
see whether we should do further changes?
Thanks,
Gerald
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.
---
htdocs/codingconventions.html | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
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
--
2.39.1
next reply other threads:[~2023-01-27 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 0:16 Gerald Pfeifer [this message]
2023-01-27 12:21 ` Jonathan Wakely
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=20230127001617.CE64D33E9E@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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: link
Be 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).