aboutsummaryrefslogtreecommitdiff
path: root/gcc/BUGS
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@dcc.unicamp.br>1998-11-01 19:52:23 +0000
committerAlexandre Oliva <oliva@gcc.gnu.org>1998-11-01 19:52:23 +0000
commit5dd21ded56058cdf62d4f8ac0ea273de95ebe268 (patch)
tree89f7c6f3c9f26f8c2fbe9196a0900a3f6208e9b2 /gcc/BUGS
parent44ba27b4d56d7a23cde0aee87be26e109815b682 (diff)
downloadgcc-5dd21ded56058cdf62d4f8ac0ea273de95ebe268.zip
gcc-5dd21ded56058cdf62d4f8ac0ea273de95ebe268.tar.gz
gcc-5dd21ded56058cdf62d4f8ac0ea273de95ebe268.tar.bz2
BUGS: fix the regexp for `more' to find the appropriate node.
* BUGS: fix the regexp for `more' to find the appropriate node. Reported by Joerg Pietschmann <joerg_pietschmann@zkb.ch> * BUGS: added link to the WWW FAQ From-SVN: r23494
Diffstat (limited to 'gcc/BUGS')
-rw-r--r--gcc/BUGS8
1 files changed, 6 insertions, 2 deletions
diff --git a/gcc/BUGS b/gcc/BUGS
index 33c9386..e628a64 100644
--- a/gcc/BUGS
+++ b/gcc/BUGS
@@ -3,7 +3,7 @@ read the Bugs section of the GCC manual for advice on
(1) how to tell when to report a bug,
(2) where to send your bug report, and
-(2) how to write a useful bug report and what information
+(3) how to write a useful bug report and what information
it needs to have.
There are three ways to read the Bugs section.
@@ -20,4 +20,8 @@ to get to the section on bugs. Or use standalone Info in
a like manner. (Standalone Info is part of the Texinfo distribution.)
(3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or
- cat /usr/local/info/gcc* | more "+/^File: emacs, Node: Bugs,"
+ cat /usr/local/info/gcc* | more "+/^File: gcc.info, Node: Bugs,"
+
+You may also want to take a look at the EGCS FAQ, in which there are
+additional instructions for submitting bug reports:
+ http://egcs.cygnus.com/faq.html#bugreport