public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 17f88fe2b73fe50b1831ece5dd40bf29151899ab Date: Fri, 27 Jan 2023 12:14:06 +0000 (GMT) [thread overview] Message-ID: <20230127121406.0ABBF3858C2C@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 17f88fe2b73fe50b1831ece5dd40bf29151899ab (commit) from 6f438ff6420ad16039c395f8302a02f44d957dae (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- 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>. ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-27 12:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230127121406.0ABBF3858C2C@sourceware.org \ --to=redi@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).