This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to update Service instructions in gcc.texi
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Patch to update Service instructions in gcc.texi
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Fri, 10 Nov 2000 12:59:52 +0000 (GMT)
- cc: <gcc-patches at gcc dot gnu dot org>
On Wed, 8 Nov 2000, Gerald Pfeifer wrote:
> On Tue, 7 Nov 2000, Joseph S. Myers wrote:
> > So what is the recommended practice for refering to individual FAQ
> > entries?
>
> Originally the plan was -- I believe Jeff suggested that -- to move the
> contents of FAQ entries like this to the regular web pages somewhere.
>
> (bugs.html would be suitable, but it's already a bit long...)
Given this, I've installed the following version of the patch, with the
FAQ reference commented out.
Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/egcs/gcc/ChangeLog,v
retrieving revision 1.8220
diff -u -r1.8220 ChangeLog
--- ChangeLog 2000/11/10 11:43:38 1.8220
+++ ChangeLog 2000/11/10 12:56:42
@@ -1,3 +1,8 @@
+2000-11-10 Joseph S. Myers <jsm28@cam.ac.uk>
+
+ * gcc.texi (Service): Update to reflect current practice and
+ location of the GNU service directory.
+
2000-11-09 Bernd Schmidt <bernds@redhat.co.uk>
* regrename.c (build_def_use): Mark contents of REG_INC notes as
Index: gcc.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/gcc.texi,v
retrieving revision 1.60
diff -u -r1.60 gcc.texi
--- gcc.texi 2000/11/04 12:42:25 1.60
+++ gcc.texi 2000/11/10 12:56:46
@@ -2808,14 +2808,22 @@
@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
--
Joseph S. Myers
jsm28@cam.ac.uk