release branch changes from 11-27 snapshot to egcs-1.0.

From-SVN: r16970

1 files changed, 16 insertions, 27 deletions

diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 83ac13bbf3f..64ed7d2dfe0 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -148,12 +148,12 @@ original English.
 @sp 1
 @c The version number appears twice more in this file.
 
-@center for version 2.7.2
+@center for egcs-1.0
 @page
 @vskip 0pt plus 1filll
 Copyright @copyright{} 1988, 89, 92, 93, 94, 95, 96 Free Software Foundation, Inc.
 @sp 2
-For GCC Version 2.7.2@*
+For EGCS Version 1.0@*
 @sp 1
 Published by the Free Software Foundation @*
 59 Temple Place - Suite 330@*
@@ -194,19 +194,19 @@ original English.
 @ifset USING
 This manual documents how to run, install and port the GNU
 compiler, as well as its new features and incompatibilities, and how to
-report bugs.  It corresponds to GNU CC version 2.7.2.
+report bugs.  It corresponds to EGCS version 1.0.
 @end ifset
 @end ifset
 
 @ifclear INTERNALS
 This manual documents how to run and install the GNU compiler,
 as well as its new features and incompatibilities, and how to report
-bugs.  It corresponds to GNU CC version 2.7.2.
+bugs.  It corresponds to EGCS version 1.0.
 @end ifclear
 @ifclear USING
 This manual documents how to port the GNU compiler,
 as well as its new features and incompatibilities, and how to report
-bugs.  It corresponds to GNU CC version 2.7.1.
+bugs.  It corresponds to EGCS version 1.0.
 @end ifclear
 
 @end ifinfo
@@ -2188,24 +2188,13 @@ for improvement of GNU CC or GNU C++ are welcome in any case.
 @node Bug Lists
 @section Where to Report Bugs
 @cindex bug report mailing lists
-@kindex bug-gcc@@prep.ai.mit.edu
-Send bug reports for GNU C to @samp{bug-gcc@@prep.ai.mit.edu}.
+@kindex egcs-bugs@@cygnus.com
+Send bug reports for GNU C to @samp{egcs-bugs@@cygnus.com}.
 
-@kindex bug-g++@@prep.ai.mit.edu
-@kindex bug-libg++@@prep.ai.mit.edu
-Send bug reports for GNU C++ to @samp{bug-g++@@prep.ai.mit.edu}.  If
-your bug involves the C++ class library libg++, send mail instead to the
-address @samp{bug-lib-g++@@prep.ai.mit.edu}.  If you're not sure, you
-can send the bug report to both lists.
-
-@strong{Do not send bug reports to @samp{help-gcc@@prep.ai.mit.edu} or
-to the newsgroup @samp{gnu.gcc.help}.} Most users of GNU CC do not want
-to receive bug reports.  Those that do, have asked to be on
-@samp{bug-gcc} and/or @samp{bug-g++}.
-
-The mailing lists @samp{bug-gcc} and @samp{bug-g++} both have newsgroups
-which serve as repeaters: @samp{gnu.gcc.bug} and @samp{gnu.g++.bug}.
-Each mailing list and its newsgroup carry exactly the same messages.
+@kindex egcs-bugs@@cygnus.com
+@kindex egcs-bugs@@cygnus.com
+Send bug reports for GNU C++ and the C++ runtime libraries to
+@samp{egcs-bugs@@cygnus.com}.
 
 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
@@ -2491,7 +2480,7 @@ we should be able to reproduce the crash ourselves.
 
 If you would like to write bug fixes or improvements for the GNU C
 compiler, that is very helpful.  Send suggested fixes to the bug report
-mailing list, @code{bug-gcc@@prep.ai.mit.edu}.
+mailing list, @code{egcs-bugs@@cygnus.com}.
 
 Please follow these guidelines so we can study your patches efficiently.
 If you don't follow these guidelines, your information might still be
@@ -2611,8 +2600,8 @@ ways to find it:
 @itemize @bullet
 @item
 Send a message to a suitable network mailing list.  First try
-@code{bug-gcc@@prep.ai.mit.edu}, and if that brings no response, try
-@code{help-gcc@@prep.ai.mit.edu}.
+@code{egcs-bugs@@cygnus.com}, and if that brings no response, try
+@code{egcs@@cygnus.com}.
 
 @item
 Look in the service directory for someone who might help you for a fee.
@@ -2625,13 +2614,13 @@ GNU CC distribution.
 
 If you would like to help pretest GNU CC releases to assure they work
 well, or if you would like to work on improving GNU CC, please contact
-the maintainers at @code{bug-gcc@@gnu.ai.mit.edu}.  A pretester should
+the maintainers at @code{egcs@@cygnus.com}.  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 @code{bug-gcc@@prep.ai.mit.edu} before you start; the
+to contact @code{egcs@@cygnus.com} before you start; the
 maintainers may be able to suggest ways to make your extension fit in
 better with the rest of GNU CC and with other development plans.