Gerald noticed these stale viewcvs links. I'll push this to trunk later
this week, and backport too.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/xml/faq.xml: Replace viewcvs links with cgit links.
* doc/xml/manual/allocator.xml: Likewise.
* doc/xml/manual/mt_allocator.xml: Likewise.
* doc/html/*: Regenerate.
---
libstdc++-v3/doc/html/api.html | 2 +-
libstdc++-v3/doc/html/faq.html | 2 +-
libstdc++-v3/doc/html/manual/memory.html | 10 +++++-----
libstdc++-v3/doc/html/manual/mt_allocator_impl.html | 6 +++---
libstdc++-v3/doc/xml/faq.xml | 2 +-
libstdc++-v3/doc/xml/manual/allocator.xml | 10 +++++-----
libstdc++-v3/doc/xml/manual/mt_allocator.xml | 6 +++---
7 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html
index b494d91f9af..d2cff093d8f 100644
--- a/libstdc++-v3/doc/html/api.html
+++ b/libstdc++-v3/doc/html/api.html
@@ -38,4 +38,4 @@
</p><p>
In addition, a rendered set of man pages are available in the same
location specified above. Start with C++Intro(3).
-</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="bk02.html">Prev</a>Â </td><td width="20%" align="center"><a accesskey="u"
href="bk02.html">Up</a></td><td width="40%" align="right">Â <a accesskey="n"
href="bk03.html">Next</a></td></tr><tr><td width="40%" align="left"
valign="top">Â </td><td width="20%" align="center"><a accesskey="h"
href="index.html">Home</a></td><td width="40%" align="right" valign="top">Â
</td></tr></table></div></body></html>
+</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="bk02.html">Prev</a>Â </td><td width="20%" align="center"><a accesskey="u"
href="bk02.html">Up</a></td><td width="40%" align="right">Â <a accesskey="n"
href="bk03.html">Next</a></td></tr><tr><td width="40%" align="left"
valign="top">Â </td><td width="20%" align="center"><a accesskey="h"
href="index.html">Home</a></td><td width="40%" align="right" valign="top">Â
</td></tr></table></div></body></html>
\ No newline at end of file
diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index dcb94ba67dc..507555839f2 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -147,7 +147,7 @@
The libstdc++ project is contributed to by several developers
all over the world, in the same way as GCC or the Linux kernel.
The current maintainers are listed in the
- <a class="link"
href="https://gcc.gnu.org/viewcvs/gcc/trunk/MAINTAINERS?view=co";
target="_top"><code class="filename">MAINTAINERS</code></a>
+ <a class="link" href="https://gcc.gnu.org/cgit/gcc/tree/MAINTAINERS";
target="_top"><code class="filename">MAINTAINERS</code></a>
file (look for "c++ runtime libs").
</p><p>
Development and discussion is held on the libstdc++ mailing
diff --git a/libstdc++-v3/doc/html/manual/memory.html
b/libstdc++-v3/doc/html/manual/memory.html
index 08ad2fd4dd8..6b707105969 100644
--- a/libstdc++-v3/doc/html/manual/memory.html
+++ b/libstdc++-v3/doc/html/manual/memory.html
@@ -120,8 +120,8 @@
Over multiple iterations, various STL container
objects have elements inserted to some maximum amount. A variety
of allocators are tested.
- Test source for <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/sequence.cc?view=markup";
target="_top">sequence</a>
- and <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/associative.cc?view=markup";
target="_top">associative</a>
+ Test source for <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert/sequence.cc";
target="_top">sequence</a>
+ and <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert/associative.cc";
target="_top">associative</a>
containers.
</p></li><li class="listitem"><p>
Insertion and erasure in a multi-threaded environment.
@@ -130,14 +130,14 @@
on a per-thread basis, as well as measuring thread contention
for memory resources.
Test source
- <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert_erase/associative.cc?view=markup";
target="_top">here</a>.
+ <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert_erase/associative.cc";
target="_top">here</a>.
</p></li><li class="listitem"><p>
A threaded producer/consumer model.
</p><p>
Test source for
- <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/sequence.cc?view=markup";
target="_top">sequence</a>
+ <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/sequence.cc";
target="_top">sequence</a>
and
- <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/associative.cc?view=markup";
target="_top">associative</a>
+ <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/associative.cc";
target="_top">associative</a>
containers.
</p></li></ol></div><p>
Since GCC 12 the default choice for
diff --git a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
index 2e5926add00..c69b9c5b55a 100644
--- a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
+++ b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
@@ -155,7 +155,7 @@ that uses it is fully constructed. For most (but not all)
STL
containers, this works, as an instance of the allocator is constructed
as part of a container's constructor. However, this assumption is
implementation-specific, and subject to change. For an example of a
-pool that frees memory, see the following
- <a class="link"
href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc?view=markup";
target="_top">
- example.</a>
+pool that frees memory, see the
+ <a class="link"
href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc";
target="_top"><code
class="filename">ext/mt_allocator/deallocate_local-6.cc</code></a>
+ example.
</p></div></div><div class="navfooter"><hr /><table width="100%"
summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p"
href="mt_allocator_design.html">Prev</a>Â </td><td width="20%"
align="center"><a accesskey="u" href="mt_allocator.html">Up</a></td><td
width="40%" align="right">Â <a accesskey="n"
href="mt_allocator_ex_single.html">Next</a></td></tr><tr><td width="40%"
align="left" valign="top">Design Issues </td><td width="20%" align="center"><a
accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right"
valign="top">Â Single Thread Example</td></tr></table></div></body></html>
\ No newline at end of file
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 4888fa93ae9..bccbb98a5a3 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -90,7 +90,7 @@
The libstdc++ project is contributed to by several developers
all over the world, in the same way as GCC or the Linux kernel.
The current maintainers are listed in the
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/viewcvs/gcc/trunk/MAINTAINERS?view=co";><filename>MAINTAINERS</filename></link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/MAINTAINERS";><filename>MAINTAINERS</filename></link>
file (look for "c++ runtime libs").
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/allocator.xml
b/libstdc++-v3/doc/xml/manual/allocator.xml
index 2418539be8d..7e74dca404a 100644
--- a/libstdc++-v3/doc/xml/manual/allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/allocator.xml
@@ -184,8 +184,8 @@
Over multiple iterations, various STL container
objects have elements inserted to some maximum amount. A variety
of allocators are tested.
- Test source for <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/sequence.cc?view=markup";>sequence</link>
- and <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/associative.cc?view=markup";>associative</link>
+ Test source for <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert/sequence.cc";>sequence</link>
+ and <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert/associative.cc";>associative</link>
containers.
</para>
@@ -200,7 +200,7 @@
on a per-thread basis, as well as measuring thread contention
for memory resources.
Test source
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert_erase/associative.cc?view=markup";>here</link>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/insert_erase/associative.cc";>here</link>.
</para>
</listitem>
@@ -210,9 +210,9 @@
</para>
<para>
Test source for
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/sequence.cc?view=markup";>sequence</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/sequence.cc";>sequence</link>
and
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/associative.cc?view=markup";>associative</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/performance/23_containers/producer_consumer/associative.cc";>associative</link>
containers.
</para>
</listitem>
diff --git a/libstdc++-v3/doc/xml/manual/mt_allocator.xml
b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
index f1c09b3bd8f..81d819d70d5 100644
--- a/libstdc++-v3/doc/xml/manual/mt_allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
@@ -307,9 +307,9 @@ that uses it is fully constructed. For most (but not all)
STL
containers, this works, as an instance of the allocator is constructed
as part of a container's constructor. However, this assumption is
implementation-specific, and subject to change. For an example of a
-pool that frees memory, see the following
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/viewcvs/gcc/trunk/libstdc++-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc?view=markup";>
- example.</link>
+pool that frees memory, see the
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc";><filename>ext/mt_allocator/deallocate_local-6.cc</filename></link>
+ example.
</para>
</section>
--
2.45.2
