Message ID | 20230127001617.CE64D33E9E@hamza.pair.com |
---|---|
State | New |
Headers | show |
Series | [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++ | expand |
On 27/01/23 01:16 +0100, Gerald Pfeifer wrote: >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? Oh wow, it's all wrong. I've pushed the patch below, thanks for pointing it out.
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