From: Joseph Myers <jsm28@cam.ac.uk>
Date: Sat, 14 Oct 2000 08:23:17 +0000 (+0100)
Subject: * gcc.texi (Contributing): Update.
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e8beb821907d460bb2720aa911b0a1bacc514c11;p=platform%2Fupstream%2Fgcc.git

* gcc.texi (Contributing): Update.

From-SVN: r36866
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3d369f7..58d28e6 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2000-10-14  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* gcc.texi (Contributing): Update.
+
 2000-10-13  Alexandre Oliva  <aoliva@redhat.com>
 
 	* c-common.c (c_expand_builtin): PARAMS-ize prototype.
diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 0c4b4c3..b215e4d 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2820,17 +2820,21 @@ GCC distribution.
 @node Contributing
 @chapter Contributing to GCC Development
 
-If you would like to help pretest GCC releases to assure they work
-well, or if you would like to work on improving GCC, please contact
-the maintainers at @email{gcc@@gcc.gnu.org}.  A pretester should
-be willing to try to investigate bugs as well as report them.
-
-If you'd like to work on improvements, please ask for suggested projects
-or suggest your own ideas.  If you have already written an improvement,
-please tell us about it.  If you have not yet started work, it is useful
-to contact @email{gcc@@gcc.gnu.org} before you start; the
-maintainers may be able to suggest ways to make your extension fit in
-better with the rest of GCC and with other development plans.
+If you would like to help pretest GCC releases to assure they work well,
+our current development sources are available by CVS (see
+@uref{http://gcc.gnu.org/cvs.html}).  Source and binary snapshots are
+also available for FTP; see @uref{http://gcc.gnu.org/snapshots.html}.
+Remember that snapshots of the current development sources may not be of
+production quality; if you find problems (whether compiler crashes,
+miscompiled code, poor optimization or any other problem), please report
+them following our bug reporting instructions at
+@uref{http://gcc.gnu.org/bugs.html}.
+
+If you would like to work on improvements to GCC, please read
+@uref{http://gcc.gnu.org/contribute.html} and
+@uref{http://gcc.gnu.org/contributewhy.html} for information on how to
+make useful contributions and avoid duplication of effort.  Suggested
+projects are listed at @uref{http://gcc.gnu.org/projects.html}.
 
 @node VMS
 @chapter Using GCC on VMS