From: Jonathan Wakely Date: Thu, 19 Jan 2017 23:15:13 +0000 (+0000) Subject: Fix typo in recent doc updates X-Git-Tag: basepoints/gcc-8~1561 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8e4160112d24d56852a17ca3627dec24d3ffa1ed;p=thirdparty%2Fgcc.git Fix typo in recent doc updates * doc/xml/manual/abi.xml: Fix typo. * doc/html/manual/abi.html: Likewise. From-SVN: r244658 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index fde7f341444e..285a90ecb00d 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,8 @@ 2017-01-19 Jonathan Wakely + * doc/xml/manual/abi.xml: Fix typo. + * doc/html/manual/abi.html: Likewise. + PR libstdc++/67085 * include/bits/predefined_ops.h (_Iter_less_val, _Val_less_iter): Add converting constructors from _Iter_less_iter. diff --git a/libstdc++-v3/doc/html/manual/abi.html b/libstdc++-v3/doc/html/manual/abi.html index 775d09e3c182..33ed3e3543fa 100644 --- a/libstdc++-v3/doc/html/manual/abi.html +++ b/libstdc++-v3/doc/html/manual/abi.html @@ -173,7 +173,7 @@ compatible. 20160427 value of the macro in the 6.1.0 release, but there are features supported in the 6.1.0 release that are not supported in 5.4.0 release. - You also can't test for the the exact values listed below to try and + You also can't test for the exact values listed below to try and identify a release, because a snapshot taken from the gcc-5-branch on 2016-04-27 would have the same value for the macro as the 6.1.0 release despite being a different version. diff --git a/libstdc++-v3/doc/xml/manual/abi.xml b/libstdc++-v3/doc/xml/manual/abi.xml index f2b2ec379622..cd7671037f3b 100644 --- a/libstdc++-v3/doc/xml/manual/abi.xml +++ b/libstdc++-v3/doc/xml/manual/abi.xml @@ -418,7 +418,7 @@ compatible. 20160427 value of the macro in the 6.1.0 release, but there are features supported in the 6.1.0 release that are not supported in 5.4.0 release. - You also can't test for the the exact values listed below to try and + You also can't test for the exact values listed below to try and identify a release, because a snapshot taken from the gcc-5-branch on 2016-04-27 would have the same value for the macro as the 6.1.0 release despite being a different version.