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

Reply via email to