* [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++
@ 2023-01-27 0:16 Gerald Pfeifer
2023-01-27 12:21 ` Jonathan Wakely
0 siblings, 1 reply; 2+ messages in thread
From: Gerald Pfeifer @ 2023-01-27 0:16 UTC (permalink / raw)
To: gcc-patches, libstdc++
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++
2023-01-27 0:16 [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++ Gerald Pfeifer
@ 2023-01-27 12:21 ` Jonathan Wakely
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Wakely @ 2023-01-27 12:21 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: gcc-patches, libstdc++
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
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.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1534 bytes --]
commit 17f88fe2b73fe50b1831ece5dd40bf29151899ab
Author: Jonathan Wakely <jwakely@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>.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-27 12:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-27 0:16 [pushed] wwwdocs: codingconventions: Update upstream instructions for libstdc++ Gerald Pfeifer
2023-01-27 12:21 ` Jonathan Wakely
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).