[PATCH] Clean up references to Subversion in documentation sources.
Jonathan Wakely
jwakely@redhat.com
Mon Jan 13 17:12:00 GMT 2020
On 13/01/20 09:09 -0700, Sandra Loosemore wrote:
>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?
I did so on the gcc-7 branch, so it says "This page describes the
C++11 support in the GCC 7 series." I have forgotten to do that on the
gcc-8 and gcc-9 branches though, so they lie. I'll do that.
>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.
Agreed.
More information about the Gcc-patches
mailing list