diff options
Diffstat (limited to 'libstdc++-v3/docs/html/17_intro/contribute.html')
| -rw-r--r-- | libstdc++-v3/docs/html/17_intro/contribute.html | 48 |
1 files changed, 30 insertions, 18 deletions
diff --git a/libstdc++-v3/docs/html/17_intro/contribute.html b/libstdc++-v3/docs/html/17_intro/contribute.html index 4f16b845d48..17bc65f4ed0 100644 --- a/libstdc++-v3/docs/html/17_intro/contribute.html +++ b/libstdc++-v3/docs/html/17_intro/contribute.html @@ -1,19 +1,23 @@ -<!--990301 slightly modified version of the GCC contribute.html file--> -<html> +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>How to contribute</title> </head> -<!--#include virtual="/include/header-subpages.html"--> +<!--990301 slightly modified version of the GCC contribute.html file--> +<!-- #include virtual="/include/header-subpages.html"--> +<body> <h2>How to contribute</h2> <p> The Standard C++ Library v3, or libstc++-2.90.x, follows an open development model. Active contributors are assigned maintainer-ship responsibility, and given write access to the CVS repository. First time submitors and all other potential contributors should follow this procedure: +</p> -<p> -<hr> +<hr /> <h4>ONE : read the documentation</h4> -<p> -<p> <ul> <li> Get and read the relevant sections of the C++ language specification. Copies of the full ISO 14882 standard are available on @@ -27,25 +31,30 @@ and their web-site is right <a href="http://www.ansi.org">here.</a> (And if you've already registered with them, clicking this link will take you to directly to the place where you can <a href="http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998">buy the standard on-line.)</a> +</li> <li> The library working group bugs, and known defects, can be obtained at these web sites: <a href="http://www.dkuug.dk/jtc1/sc22/wg21/">http://www.dkuug.dk/jtc1/sc22/wg21 </a> and <a href="http://www.comeaucomputing.com/iso/">http://www.comeaucomputing.com/iso/</a> +</li> <li> The newsgroup dedicated to standardization issues is comp.std.c++: this FAQ for this group is quite useful and can be found <a href="http://reality.sgi.com/austern_mti/std-c++/faq.html"> here </a>. +</li> <li> Peruse the <a href="http://www.gnu.ai.mit.edu/prep/standards_toc.html">GNU Coding Standards</a>, and chuckle when you hit the part about "Using Languages Other Than C." +</li> <li> Be familiar with the extensions that preceded these general GNU rules. These style issues for libstdc++ can be found in the file C++STYLE, located in the root level of the distribution, or <a href="C++STYLE"> here. </a> +</li> <li> And last but certainly not least, read the library-specific information found <a href="../documentation.html"> here.</a> +</li> </ul> -<p> -<hr> +<hr /> <h4>TWO : copyright assignment</h4> <p> Small changes can be accepted without a copyright assignment form on @@ -56,40 +65,43 @@ to fill out appropriate disclaimer forms as well. Here is the <a href="libstdc++ Please contact <a href="mailto:benjamin@cygnus.com">Benjamin Kosnik</a> if you are confused about the assignment or have general licensing questions. +</p> -<p> -<hr> +<hr /> <h4>THREE : submitting patches</h4> -<p> +<p> Every patch must have several pieces of information before it can be properly evaluated. Ideally (and to ensure the fastest possible response from the maintainers) it would have all of these pieces: -<p> +</p> + <ul> <li> A description of the bug and how your patch fixes this bug. For - new features a description of the feature and your implementation. + new features a description of the feature and your implementation. </li> <li> A ChangeLog entry as plaintext; see the various ChangeLog files for format and content. If using you are using emacs as your editor, simply position the insertion point at the beginning of your change and hit CX-4a to bring up the appropriate ChangeLog - entry. See--magic! Similar functionality also exists for vi. + entry. See--magic! Similar functionality also exists for vi. </li> <li> A testsuite submission or sample program that will easily and - simply show the existing error or test new functionality. + 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. + get the latest version of GNU diff. </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 -discussion should be sent to the libstdc++ mailinglist. +discussion should be sent to the libstdc++ mailinglist. </li> </ul> +</body> +</html> |