This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3 patch] update references to CVS in libstdc++ docs
On 01/10/2007, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> That's the bit I meant, yes. Thanks for the pointer to the new files,
> I'll update the links before I checkin.
I think I found the right files to link to. Some of the descriptions
in the docs didn't seem relevant now, so I edited the text.
The final checkin (as attached) adds a link from the bottom of
17_intro/contribute.html to http://gcc.gnu.org/wiki/SvnTricks for info
on customising the output of "svn diff" (my update to the docs removes
the request to use the -cp diff options when using "svn diff" - let me
know if you want me to restore something equivalent.) I also updated
the "Legal Issues" link higher up on that same page, since the
original link gets redirected by gnu.org.
Jon
Index: docs/html/test.html
===================================================================
--- docs/html/test.html (revision 128908)
+++ docs/html/test.html (working copy)
@@ -319,7 +319,7 @@
<p>
All files are copyright the FSF, and GPL'd: this is very
important. The first copyright year should correspond to the date
- the file was checked in to CVS.
+ the file was checked in to SVN.
</p>
<p>
Index: docs/html/ext/mt_allocator.html
===================================================================
--- docs/html/ext/mt_allocator.html (revision 128908)
+++ docs/html/ext/mt_allocator.html (working copy)
@@ -51,7 +51,7 @@
</p>
<p>
-The aim of this document is to describe - from a application point of
+The aim of this document is to describe - from an application point of
view - the "inner workings" of the allocator.
</p>
@@ -67,11 +67,12 @@
</p>
<p>The datum describing pools characteristics is
- <pre>
- template<bool _Thread>
- class __pool
- </pre>
-This class is parametrized on thread support, and is explicitly
+</p>
+<pre>
+ template<bool _Thread>
+ class __pool
+</pre>
+<p> This class is parametrized on thread support, and is explicitly
specialized for both multiple threads (with <code>bool==true</code>)
and single threads (via <code>bool==false</code>.) It is possible to
use a custom pool datum instead of the default class that is provided.
@@ -102,11 +103,12 @@
</p>
<p> Putting this all together, the actual allocator class is
+</p>
<pre>
template<typename _Tp, typename _Poolp = __default_policy>
class __mt_alloc : public __mt_alloc_base<_Tp>, _Poolp
</pre>
-This class has the interface required for standard library allocator
+<p> This class has the interface required for standard library allocator
classes, namely member functions <code>allocate</code> and
<code>deallocate</code>, plus others.
</p>
@@ -116,7 +118,7 @@
</h3>
<p>Certain allocation parameters can be modified, or tuned. There
-exists a nested <pre>struct __pool_base::_Tune</pre> that contains all
+exists a nested <code>struct __pool_base::_Tune</code> that contains all
these parameters, which include settings for
</p>
<ul>
@@ -301,7 +303,7 @@
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 href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc%2b%2b-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc";>
+ <a href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/ext/mt_allocator/deallocate_local-6.cc?view=markup";>
example.</a>
</p>
Index: docs/html/ext/tr1.html
===================================================================
--- docs/html/ext/tr1.html (revision 128908)
+++ docs/html/ext/tr1.html (working copy)
@@ -36,7 +36,7 @@
</p>
<p>
-This page describes the TR1 support in mainline GCC CVS, not in any particular
+This page describes the TR1 support in mainline GCC SVN, not in any particular
release.
</p>
Index: docs/html/17_intro/contribute.html
===================================================================
--- docs/html/17_intro/contribute.html (revision 128908)
+++ docs/html/17_intro/contribute.html (working copy)
@@ -17,7 +17,7 @@
<h2>How to contribute</h2>
<p> The Standard C++ Library v3, follows an open development
model. Active contributors are assigned maintainer-ship
-responsibility, and given write access to the CVS repository. First
+responsibility, and given write access to the SVN repository. First
time contributors should follow this procedure:
</p>
@@ -81,14 +81,15 @@
<p>
For more information about getting a copyright assignment, please see
-<a href=http://www.gnu.org/prep/maintain_4.html#SEC4=> Legal Issues</a>
+<a href="http://www.gnu.org/prep/maintain/html_node/Legal-Matters.html";>Legal
+Matters</a>.
</p>
<p>
Please contact <a href="mailto:bkoz+assign@redhat.com";>Benjamin
Kosnik</a> if you are confused about the assignment or have general
licensing questions. When requesting an assignment form from <a
-HREF="mailto:assign@gnu.org";>assign@gnu.org</a>, please cc
+href="mailto:assign@gnu.org";>assign@gnu.org</a>, please cc
the above libstdc++ maintainer so that progress can be monitored.
</p>
@@ -116,10 +117,12 @@
<li> A testsuite submission or sample program that will easily and
simply show the existing error or test new functionality. </li>
- <li> The patch itself. If you are accessing the CVS repository at
- Cygnus, use "cvs update; cvs diff -c3p NEW"; else, use "diff -c3p OLD
- NEW" ... If your version of diff does not support these options, then
- get the latest version of GNU diff. </li>
+ <li> The patch itself. If you are accessing the SVN repository
+ use "svn update; svn diff NEW"; else, use "diff -cp OLD NEW"
+ ... If your version of diff does not support these options, then
+ get the latest version of GNU diff. The <a
+ href="http://gcc.gnu.org/wiki/SvnTricks";>SVN Tricks</a> wiki page
+ has information on customising the output of <code>svn diff</code>.</li>
<li> When you have all these pieces, bundle them up in a mail message
and send it to libstdc++@gcc.gnu.org. All patches and related
Index: docs/html/documentation.html
===================================================================
--- docs/html/documentation.html (revision 128908)
+++ docs/html/documentation.html (working copy)
@@ -244,7 +244,7 @@
<h2><a name="5">Contributor-Specific Information</a></h2>
<ul>
<li><a href="17_intro/contribute.html">Contributor checklist</a></li>
- <li><a href="http://gcc.gnu.org/cvswrite.html";>Getting CVS write access
+ <li><a href="http://gcc.gnu.org/svnwrite.html";>Getting SVN write access
(look for "Write after approval")</a></li>
<li><a href="17_intro/BADNAMES">BADNAMES</a>
- names to avoid because of potential collisions</li>
Index: docs/html/20_util/allocator.html
===================================================================
--- docs/html/20_util/allocator.html (revision 128908)
+++ docs/html/20_util/allocator.html (working copy)
@@ -179,27 +179,27 @@
<li>Insertion. Over multiple iterations, various STL container
objects have elements inserted to some maximum amount. A variety
of allocators are tested.
- Test source <a
- href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc%2b%2b-v3/testsuite/performance/20_util/allocator/insert.cc?only_with_tag=MAIN";>here.</a>
+ Test source for <a
+ href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/sequence.cc?view=markup";>sequence</a>
+ and <a
+ href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert/associative.cc?view=markup";>associative</a>
+ containers.
</li>
- <li>Insertion, clear, and re-insertion in a multi-threaded
- environment. Over multiple iterations, several threads are
- started that insert elements into a STL container, then assign a
- null instance of the same type to clear memory, and then
- re-insert the same number of elements. Several STL containers and
- multiple allocators are tested. This test shows the ability of
- the allocator to reclaim memory on a pre-thread basis, as well as
- measuring thread contention for memory resources.
+ <li>Insertion and erasure in a multi-threaded environment.
+ This test shows the ability of the allocator to reclaim memory
+ on a pre-thread basis, as well as measuring thread contention
+ for memory resources.
Test source
- <a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc%2b%2b-v3/testsuite/performance/20_util/allocator/insert_insert.cc";>
- here.</a>
+ <a href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/insert_erase/associative.cc?view=markup";>here</a>.
</li>
<li>A threaded producer/consumer model.
- Test source
- <a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc%2b%2b-v3/testsuite/performance/20_util/allocator/producer_consumer.cc";>
- here.</a>
+ Test source for
+ <a href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/producer_consumer/sequence.cc?view=markup";>sequence</a>
+ and
+ <a href="http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/testsuite/performance/23_containers/producer_consumer/associative.cc?view=markup";>associative</a>
+ containers.
</li>
</ul>
@@ -490,7 +490,7 @@
</p>
<p>
- Berger, Emery with Ben Zorn & Kathryn McKinley, OOPSLA 2002
+ Berger, Emery with Ben Zorn & Kathryn McKinley, OOPSLA 2002
<a href="http://www.cs.umass.edu/~emery/pubs/berger-oopsla2002.pdf";>Reconsidering Custom Memory Allocation</a>
</p>