PATCH: gcc.texi and bug reporting instructions

[Gerald Pfeifer]

I had promised to address our bug reporting instructions, and this is
a first cleanup. KISS.

2001-01-16  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

 	* gcc.texi (Bug Lists): Do not mention newsgroups nor the
 	possibility to report bugs via postal mail. Change a URL and
 	merge in a nearly duplicate statement...
 	(Bug Reporting): ...from here.
 	(Service): Refer to the Bug Reporting section instead of
 	duplicating an URL.
 	(Contributing): Remove trivial explanations concerning snapshots.

Passed a full bootstrap (sic!) on i386-unknown-freebsd4.2. Installed.

Gerald

Index: gcc.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/gcc.texi,v
retrieving revision 1.71
diff -c -3 -p -r1.71 gcc.texi
*** gcc.texi	2001/01/15 21:12:14	1.71
--- gcc.texi	2001/01/16 19:27:48
*************** convention, in which bug reports for too
*** 2449,2480 ****
  to @samp{bug-foo@@gnu.org}, the address @email{bug-gcc@@gnu.org}
  may also be used; it will forward to the address given above.

! Please read @uref{ http://www.gnu.org/software/gcc/bugs.html} for
! bug reporting instructions before you post a bug report.

- Often people think of posting bug reports to the newsgroup instead of
- mailing them.  This appears to work, but it has one problem which can be
- crucial: a newsgroup posting does not contain a mail path back to the
- sender.  Thus, if maintainers need more information, they may be unable
- to reach you.  For this reason, you should always send bug reports by
- mail to the proper mailing list.
-
- As a last resort, send bug reports on paper to:
-
- @example
- GNU Compiler Bugs
- Free Software Foundation
- 59 Temple Place - Suite 330
- Boston, MA 02111-1307, USA
- @end example
-
  @node Bug Reporting,gccbug,Bug Lists,Bugs
  @section How to Report Bugs
  @cindex compiler bugs, reporting

- You may find additional and/or more up-to-date instructions at
- @uref{ http://www.gnu.org/software/gcc/bugs.html} .
-
  The fundamental principle of reporting bugs usefully is this:
  @strong{report all the facts}.  If you are not sure whether to state a
  fact or leave it out, state it!
--- 2449,2461 ----
  to @samp{bug-foo@@gnu.org}, the address @email{bug-gcc@@gnu.org}
  may also be used; it will forward to the address given above.

! Please read @uref{ http://gcc.gnu.org/bugs.html} for additional and/or
! more up-to-date bug reporting instructions before you post a bug report.

  @node Bug Reporting,gccbug,Bug Lists,Bugs
  @section How to Report Bugs
  @cindex compiler bugs, reporting

  The fundamental principle of reporting bugs usefully is this:
  @strong{report all the facts}.  If you are not sure whether to state a
  fact or leave it out, state it!
*************** Send a message to a suitable network mai
*** 2988,2994 ****
  that brings no response, try @email{gcc@@gcc.gnu.org}.  For help
  changing GCC, ask @email{gcc@@gcc.gnu.org}.  If you think you have found
  a bug in GCC, please report it following the instructions at
! @uref{ http://gcc.gnu.org/bugs.html} .

  @item
  Look in the service directory for someone who might help you for a fee.
--- 2969,2975 ----
  that brings no response, try @email{gcc@@gcc.gnu.org}.  For help
  changing GCC, ask @email{gcc@@gcc.gnu.org}.  If you think you have found
  a bug in GCC, please report it following the instructions at
! @pxref{Bug Reporting}.

  @item
  Look in the service directory for someone who might help you for a fee.
*************** If you would like to help pretest GCC re
*** 3008,3018 ****
  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
--- 2989,2994 ----