Rework libstdc++ contributing docs

Message ID
State New
Headers show

Commit Message

Jonathan Wakely April 2, 2013, 12:09 a.m.
At Gerald's suggestion this reworks the libstdc++ contributing docs to
refer to the general GCC contributing docs instead of repeating the
same info.

        * doc/xml/manual/appendix_contributing.xml: Remove broken link and
        defer to general documentation on contributing to GCC.
        * doc/html/*: Regenerate.

Committed to trunk.


diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index ab69093..f5dc67f 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
@@ -18,9 +18,12 @@ 
-  The GNU C++ Library follows an open development model. Active
-  contributors are assigned maintainer-ship responsibility, and given
-  write access to the source repository. First time contributors
+  The GNU C++ Library is part of GCC and follows the same development model,
+  so the general rules for
+  <link xmlns:xlink="" xlink:href="">contributing
+  to GCC</link> apply. Active
+  contributors are assigned maintainership responsibility, and given
+  write access to the source repository. First-time contributors
   should follow this procedure:
@@ -44,7 +47,7 @@ 
 	  organization is
 	  <link xmlns:xlink="" xlink:href="">ANSI</link>.
 	  (And if you've already registered with them you can
-	  <link xmlns:xlink="" xlink:href="">buy the standard on-line</link>.)
+	  <link xmlns:xlink="" xlink:href="">buy the standard on-line</link>.)
@@ -58,15 +61,6 @@ 
-	  The newsgroup dedicated to standardization issues is
-	  comp.std.c++: the
-	  <link xmlns:xlink="" xlink:href="">FAQ</link>
-          for this group is quite useful.
-      </para>
-      </listitem>
-      <listitem>
-	<para>
 	  the <link xmlns:xlink="" xlink:href="">GNU
 	  Coding Standards</link>, and chuckle when you hit the part
@@ -95,10 +89,7 @@ 
   <section xml:id="list.copyright"><info><title>Assignment</title></info>
-      Small changes can be accepted without a copyright assignment form on
-      file. New code and additions to the library need completed copyright
-      assignment form on file at the FSF. Note: your employer may be required
-      to fill out appropriate disclaimer forms as well.
+      See the <link xmlns:xlink="" xlink:href="">legal prerequisites</link> for all GCC contributions.
@@ -119,12 +110,6 @@ 
-      For more information about getting a copyright assignment, please see
-      <link xmlns:xlink="" xlink:href="">Legal
-	Matters</link>.
-    </para>
-    <para>
       Please contact Benjamin Kosnik at
       <email></email> if you are confused
       about the assignment or have general licensing questions. When