diff options
author | redi <> | 2007-10-01 19:39:08 +0000 |
---|---|---|
committer | redi <> | 2007-10-01 19:39:08 +0000 |
commit | ed518ef85709503b7a92a778560b713a5b84a61e (patch) | |
tree | 11a0a9f5135d01a085a8b5ebe1e459709411deaf /libstdc++-v3/docs/html/17_intro/contribute.html | |
parent | 264ee351757fee0fabf67b16a5f6d9b91029d452 (diff) |
* docs/html/test.html, docs/html/ext/mt_allocator.html,
docs/html/ext/tr1.html, docs/html/17_intro/contribute.html,
docs/html/documentation.html, docs/html/20_util/allocator.html:
Update docs to refer to Subversion not CVS. Fix markup.
Diffstat (limited to 'libstdc++-v3/docs/html/17_intro/contribute.html')
-rw-r--r-- | libstdc++-v3/docs/html/17_intro/contribute.html | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/libstdc++-v3/docs/html/17_intro/contribute.html b/libstdc++-v3/docs/html/17_intro/contribute.html index 0013d604925..00c749a4490 100644 --- a/libstdc++-v3/docs/html/17_intro/contribute.html +++ b/libstdc++-v3/docs/html/17_intro/contribute.html @@ -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 @@ this question would be appreciated. <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 @@ response from the maintainers) it would have all of these pieces: <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 |