From: Sandra Loosemore <sandra@codesourcery.com>
To: "Eric S. Raymond" <esr@thyrsus.com>, <gcc-patches@gcc.gnu.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Clean up references to Subversion in documentation sources.
Date: Mon, 13 Jan 2020 16:13:00 -0000 [thread overview]
Message-ID: <3f91720b-c6b3-533f-de39-26f200f5cc34@codesourcery.com> (raw)
In-Reply-To: <20200113140202.GA63759@thyrsus.com>
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
> Clean up references to SVN in in the GCC docs, redirecting to Git
> documentation as appropriate.
This is OK, although the set of changes for the libstdc++ manual like
this gave me pause:
> diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> index 2b05ff6601a..cf5722377a6 100644
> --- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> +++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> @@ -18,7 +18,7 @@ This status table is based on the table of contents of ISO/IEC 14882:2003.
> </para>
>
> <para>
> -This page describes the C++ support in mainline GCC SVN, not in any
> +This page describes the C++ support in mainline GCC, not in any
> particular release.
> </para>
IIUC the statements being modified here are incorrect; since the manuals
are packaged with the GCC sources, they go in lock step with the source
version, and the text of the manual describes the GCC version being
built, not mainline. Perhaps the libstdc++ documentation maintainers
would like to correct this separately?
For similar reasons, I suggest backporting this patch to all active GCC
release branches, namely GCC 8 and GCC 9, so that manuals packaged with
upcoming releases from those branches will correctly point to the GIT
repository instead of SVN.
-Sandra
next parent reply other threads:[~2020-01-13 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200113140202.GA63759@thyrsus.com>
2020-01-13 16:13 ` Sandra Loosemore [this message]
2020-01-13 16:21 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:12 ` Jonathan Wakely
2020-01-13 21:41 ` Eric S. Raymond
2020-01-28 13:28 ` Segher Boessenkool
2020-01-20 8:24 ` Sandra Loosemore
2020-01-21 22:27 ` Jonathan Wakely
2020-01-13 16:49 ` Jonathan Wakely
2020-01-13 17:24 ` Jonathan Wakely
2020-01-14 16:50 ` Gerald Pfeifer
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=3f91720b-c6b3-533f-de39-26f200f5cc34@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=esr@thyrsus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@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: link
Be 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).