* gcc.texi: More changes related to list conversion.

        * invoke.texi: Likewise.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@28250 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index a243a37..901e413 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+Sun Jul 25 21:40:33 1999  Jeffrey A Law  (law@cygnus.com)
+
+       * gcc.texi: More changes related to list conversion.
+       * invoke.texi: Likewise.
+
 Sun Jul 25 18:15:39 1999  Richard Henderson  <rth@cygnus.com>
 
        * builtins.c (expand_builtin_saveregs): Remove static, remove exp

diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 1c6a25e..925a1f4 100644 (file)
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2674,13 +2674,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@@egcs.cygnus.com}.  A pretester should
+the maintainers at @code{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 @code{egcs@@egcs.cygnus.com} before you start; the
+to contact @code{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 GNU CC and with other development plans.
 

diff --git a/gcc/invoke.texi b/gcc/invoke.texi
index 12f3682..4648143 100644 (file)
--- a/gcc/invoke.texi
+++ b/gcc/invoke.texi
@@ -2503,7 +2503,7 @@ These two options are intended to be removed someday, once
 they have helped determine the efficacy of various
 approaches to improving loop optimizations.
 
-Please let us (@code{egcs@@egcs.cygnus.com} and @code{fortran@@gnu.org})
+Please let us (@code{gcc@@gcc.gnu.org} and @code{fortran@@gnu.org})
 know how use of these options affects
 the performance of your production code.
 We're very interested in code that runs @emph{slower}