aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeffrey A Law <law@cygnus.com>1999-08-05 09:16:27 +0000
committerJeff Law <law@gcc.gnu.org>1999-08-05 03:16:27 -0600
commit82fb18dd276a481075cc8d01b6727e45f9c2bc7b (patch)
tree0e2b2e8edbe6fb3caad75db9935d0f1b94daffde
parent4adfda4eeeaa1f7a5f9f5cfbf06604a6ac8be6ff (diff)
downloadgcc-82fb18dd276a481075cc8d01b6727e45f9c2bc7b.zip
gcc-82fb18dd276a481075cc8d01b6727e45f9c2bc7b.tar.gz
gcc-82fb18dd276a481075cc8d01b6727e45f9c2bc7b.tar.bz2
gcc.c: Update URLs and mail addresses.
* gcc.c: Update URLs and mail addresses. * gcc.texi: Likewise. From-SVN: r28535
-rw-r--r--gcc/ChangeLog5
-rw-r--r--gcc/gcc.c4
-rw-r--r--gcc/gcc.texi12
3 files changed, 13 insertions, 8 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 94bd0c9..29a2a6d 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+Thu Aug 5 02:40:42 1999 Jeffrey A Law (law@cygnus.com)
+
+ * gcc.c: Update URLs and mail addresses.
+ * gcc.texi: Likewise.
+
Thu Aug 5 01:14:13 1999 Daniel Jacobowitz <drow@false.org>
* rs6000.c (current_file_function_operand): Return zero for
diff --git a/gcc/gcc.c b/gcc/gcc.c
index cf84e51..b309206 100644
--- a/gcc/gcc.c
+++ b/gcc/gcc.c
@@ -4984,7 +4984,7 @@ main (argc, argv)
if (! verbose_flag)
{
printf ("\nFor bug reporting instructions, please see:\n");
- printf ("<URL:http://gcc.gnu.org/faq.html#bugreport>.\n");
+ printf ("<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>.\n");
exit (0);
}
@@ -5177,7 +5177,7 @@ main (argc, argv)
if (print_help_list)
{
printf ("\nFor bug reporting instructions, please see:\n");
- printf ("<URL:http://gcc.gnu.org/faq.html#bugreport>\n");
+ printf ("<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>\n");
}
exit (error_count > 0 ? (signal_count ? 2 : 1) : 0);
diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 8b478c6..a4820d9 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2256,11 +2256,11 @@ for improvement of GCC are welcome in any case.
@node Bug Lists
@section Where to Report Bugs
@cindex bug report mailing lists
-@kindex gcc-bugs@@gcc.gnu.org
+@kindex gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org
Send bug reports for the GNU Compiler Collection to
-@samp{gcc-bugs@@gcc.gnu.org}.
+@samp{gcc-bugs@@gcc.gnu.org} or @samp{bug-gcc@gnu.org}.
-Please read @samp{<URL:http://gcc.gnu.org/faq.html#bugreport>} for
+Please read @samp{<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>} for
bug reporting instructions before you post a bug report.
Often people think of posting bug reports to the newsgroup instead of
@@ -2284,7 +2284,7 @@ Boston, MA 02111-1307, USA
@cindex compiler bugs, reporting
You may find additional and/or more up-to-date instructions at
-@samp{<URL:http://gcc.gnu.org/faq.html#bugreport>}.
+@samp{<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>}.
The fundamental principle of reporting bugs usefully is this:
@strong{report all the facts}. If you are not sure whether to state a
@@ -2664,8 +2664,8 @@ ways to find it:
@itemize @bullet
@item
Send a message to a suitable network mailing list. First try
-@code{gcc-bugs@@gcc.gnu.org}, and if that brings no response, try
-@code{gcc@@gcc.gnu.org}.
+@code{gcc-bugs@@gcc.gnu.org} or @code{bug-gcc@gnu.org}, and if that
+brings no response, try @code{gcc@@gcc.gnu.org}.
@item
Look in the service directory for someone who might help you for a fee.