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.


commit 17f88fe2b73fe50b1831ece5dd40bf29151899ab
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Fri Jan 27 12:13:42 2023 +0000

    Replace outdated info about libstdc++-v3/doc files

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 24365815..7e2a092d 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -754,13 +754,13 @@ autoconf-based configury is a local GCC invention.  Changes to zlib
 outside the build system are discouraged, and should be sent upstream
 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 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
-without prior permission, if at all.</li>
+<li>libstdc++-v3:  The doc/doxygen/user.cfg.in file is partially autogenerated
+from <a href="https://www.doxygen.nl";>the Doxygen tool</a> (and regenerated
+using <tt>doxygen -u</tt>).
+The files in doc/html are generated from the Docbook sources in doc/xml
+and should not be changed manually.
+The files in doc/xml/gnu are based on the GNU licenses and should not
+be changed without prior permission, if at all.</li>
 
 <li>libgcc/config/libbid: The master sources come from Intel BID library
 <a href="https://netlib.org/misc/intel/";>Intel BID library</a>. 

Reply via email to