Patch to gcc.texi: update contributing info (was: Re: Unifying BugReporting Instructions)

[Joseph S. Myers]

On Fri, 13 Oct 2000, Gerald Pfeifer wrote:

> > 1) The documentation should probably emphasise that the use of GNATS -
> > either through the gccbug script or GNATSweb - is to be preferred
> 
> Yes, in fact I have been planing to do so. Once Alexandre has committed
> the changes to bugs.html we discussed yesterday, I'm going to do so --
> unless you beat me to it (i.e., consider such a change pre-approved). :-)

This patch does something else vaguely related: it updates the information
in gcc.texi on contributing to GCC to relate to current reality and refer
to the web pages for most information.  It passes "make info".  OK to
commit?

[Political question: is the manual supposed to be giving URLs on
gcc.gnu.org or under http://www.gnu.org/software/gcc/ ?]

2000-10-13  Joseph S. Myers  <jsm28@cam.ac.uk>

	* gcc.texi (Contributing): Update.

--- gcc.texi.orig	Thu Oct 12 09:29:34 2000
+++ gcc.texi	Fri Oct 13 11:47:38 2000
@@ -2820,17 +2820,21 @@
 @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 would like to help pretest GCC releases to assure they work well,
+our current development sources are available by anonymous 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'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 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

-- 
Joseph S. Myers
jsm28@cam.ac.uk