public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
	gcc-patches@gcc.gnu.org,	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 17:24:00 -0000	[thread overview]
Message-ID: <20200113164918.GC60955@redhat.com> (raw)
In-Reply-To: <20200113162121.GB60955@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

On 13/01/20 16:21 +0000, Jonathan Wakely wrote:
>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.

Here's what I've committed to releases/gcc-9, I'll do something
similar for gcc-8.



[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 4640 bytes --]

commit c6f60a62b0b89a0f8c252970f3a4cf0bc2d220ce
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Jan 13 16:25:01 2020 +0000

    libstdc++: Fix documentation claiming to refer to mainline
    
            * doc/xml/manual/status_cxx1998.xml: Replace incorrect statement
            about documenting mainline.
            * doc/xml/manual/status_cxx2011.xml: Likewise.
            * doc/xml/manual/status_cxx2014.xml: Likewise.
            * doc/xml/manual/status_cxx2017.xml: Likewise.
            * doc/xml/manual/status_cxx2020.xml: Likewise.
            * doc/xml/manual/status_cxxtr1.xml: Likewise.
            * doc/xml/manual/status_cxxtr24733.xml: Likewise.
            * doc/html/*: Regenerate.

diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
index 2b05ff6601a..44a042c2724 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
@@ -18,8 +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
-particular release.
+This page describes the C++ support in the GCC 9 series.
 </para>
 
 <!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
index 0fa4bc0dffe..568102823b0 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
@@ -27,8 +27,7 @@ presence of the required flag.
 </para>
 
 <para>
-This page describes the C++11 support in mainline GCC SVN, not in any
-particular release.
+This page describes the C++11 support in the GCC 9 series.
 </para>
 
 <!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
index a33b4ec1611..7b604307c8e 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
@@ -20,8 +20,7 @@ presence of the required flag.
 </para>
 
 <para>
-This page describes the C++14 and library TS support in mainline GCC SVN,
-not in any particular release.
+This page describes the C++14 and library TS support in the GCC 9 series.
 </para>
 
 <table frame="all" xml:id="table.cxx14_status">
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 40fe7cd2037..e1513142415 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -20,8 +20,7 @@ presence of the required flag.
 </para>
 
 <para>
-This section describes the C++17 and library TS support in mainline GCC SVN,
-not in any particular release.
+This section describes the C++17 and library TS support in the GCC 9 series.
 </para>
 
 <para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
index ccf38185a6c..fc7fe0a3d9f 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
@@ -20,8 +20,7 @@ presence of the required flag.
 </para>
 
 <para>
-This section describes the C++20 and library TS support in mainline GCC SVN,
-not in any particular release.
+This section describes the C++20 and library TS support in the GCC 9 series.
 </para>
 
 <para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
index 32ad20a2fb2..c1e65752156 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
@@ -22,8 +22,7 @@ In this implementation the header names are prefixed by
 </para>
 
 <para>
-This page describes the TR1 support in mainline GCC SVN, not in any particular
-release.
+This page describes the TR1 support in the GCC 9 series.
 </para>
 
 <!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
index e8d445116a2..a3ea8b285f6 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
@@ -16,8 +16,7 @@ decimal floating-point arithmetic
 </para>
 
 <para>
-This page describes the TR 24733 support in mainline GCC SVN, not in any
-particular release.
+This page describes the TR 24733 support in the GCC 9 series.
 </para>
 
 <!-- Status is Yes or No, Broken/Partial-->

  reply	other threads:[~2020-01-13 16:49 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
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 [this message]
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=20200113164918.GC60955@redhat.com \
    --to=jwakely@redhat.com \
    --cc=esr@thyrsus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=sandra@codesourcery.com \
    /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).