* gcc.c, gcc.texi: Update email addresses.

From-SVN: r25057

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index fcfabb09ae29218ee7332439d1c7a9ed4d8513a7..d8a8f2b3cbe51c2c82be580a22e5466fabdc6b6c 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+Sat Feb  6 16:03:36 1999  Jeffrey A Law  (law@cygnus.com)
+
+       * gcc.c, gcc.texi: Update email addresses.
+
 Sat Jan 30 05:27:25 1999  Jeffrey A Law  (law@cygnus.com)
 
        Thu Jan 21 01:59:30 1999  Richard Henderson  <rth@cygnus.com>

diff --git a/gcc/gcc.c b/gcc/gcc.c
index c186df3001140dd31a2a06c1caf7328827699140..e319db9941cb3cd4bd42fcc2ad5b97c8e08d9d5b 100644 (file)
--- a/gcc/gcc.c
+++ b/gcc/gcc.c
@@ -4947,7 +4947,7 @@ main (argc, argv)
 
       if (! verbose_flag)
        {
-         printf ("\nReport bugs to egcs-bugs@cygnus.com.\n");
+         printf ("\nReport bugs to egcs-bugs@egcs.cygnus.com.\n");
          printf ("Please see the file BUGS (included with the sources) first.\n");
          
          exit (0);
@@ -5137,7 +5137,7 @@ main (argc, argv)
 
   if (print_help_list)
     {
-      printf ("\nReport bugs to egcs-bugs@cygnus.com.\n");
+      printf ("\nReport bugs to egcs-bugs@egcs.cygnus.com.\n");
       printf ("Please see the file BUGS (included with the sources) first.\n");
     }
   

diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 7e89624474139b686867e9aa5109ef8bfb985252..87d4c7b12379b1e43f28b4a550394c355eb56eea 100644 (file)
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2188,13 +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 egcs-bugs@@cygnus.com
-Send bug reports for GNU C to @samp{egcs-bugs@@cygnus.com}.
+@kindex egcs-bugs@@egcs.cygnus.com
+Send bug reports for GNU C to @samp{egcs-bugs@@egcs.cygnus.com}.
 
-@kindex egcs-bugs@@cygnus.com
-@kindex egcs-bugs@@cygnus.com
+@kindex egcs-bugs@@egcs.cygnus.com
+@kindex egcs-bugs@@egcs.cygnus.com
 Send bug reports for GNU C++ and the C++ runtime libraries to
-@samp{egcs-bugs@@cygnus.com}.
+@samp{egcs-bugs@@egcs.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
@@ -2480,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{egcs-bugs@@cygnus.com}.
+mailing list, @code{egcs-bugs@@egcs.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
@@ -2600,8 +2600,8 @@ ways to find it:
 @itemize @bullet
 @item
 Send a message to a suitable network mailing list.  First try
-@code{egcs-bugs@@cygnus.com}, and if that brings no response, try
-@code{egcs@@cygnus.com}.
+@code{egcs-bugs@@egcs.cygnus.com}, and if that brings no response, try
+@code{egcs@@egcs.cygnus.com}.
 
 @item
 Look in the service directory for someone who might help you for a fee.
@@ -2614,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{egcs@@cygnus.com}.  A pretester should
+the maintainers at @code{egcs@@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{egcs@@cygnus.com} before you start; the
+to contact @code{egcs@@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.