From: jsm28 Date: Fri, 10 Nov 2000 12:58:07 +0000 (+0000) Subject: * gcc.texi (Service): Update to reflect current practice and X-Git-Url: http://git.sourceforge.jp/view?a=commitdiff_plain;h=afa1da6ec4d2acea6ccc0dca40aa8da2b820f0b0;p=pf3gnuchains%2Fgcc-fork.git * gcc.texi (Service): Update to reflect current practice and location of the GNU service directory. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@37366 138bc75d-0d04-0410-961f-82ee72b054a4 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 9625f27804b..6d995eaa728 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2000-11-10 Joseph S. Myers + + * gcc.texi (Service): Update to reflect current practice and + location of the GNU service directory. + 2000-11-09 Bernd Schmidt * regrename.c (build_def_use): Mark contents of REG_INC notes as diff --git a/gcc/gcc.texi b/gcc/gcc.texi index c7cd04d6ef0..6e8972ab063 100644 --- a/gcc/gcc.texi +++ b/gcc/gcc.texi @@ -2808,15 +2808,23 @@ ways to find it: @itemize @bullet @item Send a message to a suitable network mailing list. First try -@email{gcc-bugs@@gcc.gnu.org} or @email{bug-gcc@@gnu.org}, and if that -brings no response, try @email{gcc@@gcc.gnu.org}. +@email{gcc-help@@gcc.gnu.org} (for help installing or using GCC), and if +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. -The service directory is found in the file named @file{SERVICE} in the -GCC distribution. +The service directory is found at +@uref{http://www.gnu.org/prep/service.html}. @end itemize +@c For further information, see +@c @uref{http://gcc.gnu.org/cgi-bin/fom.cgi?file=12}. +@c FIXME: this URL may be too volatile, this FAQ entry needs to move to +@c the regular web pages before we can uncomment the reference. + @node Contributing @chapter Contributing to GCC Development