From 674e9baac9f5237e7d935e85aee0a2f7fa48eb3f Mon Sep 17 00:00:00 2001
From: Wolfgang Bangerth <bangerth@dealii.org>
Date: Fri, 16 May 2003 09:02:19 -0600
Subject: [PATCH] * doc/bugreport.texi, f/g77.texi: Remove most of the preface
of the bug reporting section.
From-SVN: r66863
---
gcc/ChangeLog | 5 +++++
gcc/doc/bugreport.texi | 13 -------------
gcc/f/ChangeLog | 5 +++++
gcc/f/g77.texi | 22 ++--------------------
4 files changed, 12 insertions(+), 33 deletions(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index b0f3450d14de..52c7faeb5fba 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2003-05-16 Wolfgang Bangerth <bangerth@dealii.org>
+
+ * doc/bugreport.texi: Remove most of the of the preface of the
+ bugs section.
+
2003-05-16 Jakub Jelinek <jakub@redhat.com>
* config/ia64/unwind-ia64.c (uw_update_reg_address): Handle
diff --git a/gcc/doc/bugreport.texi b/gcc/doc/bugreport.texi
index 4ca9ca6a5a2f..d9613ef6d1cc 100644
--- a/gcc/doc/bugreport.texi
+++ b/gcc/doc/bugreport.texi
@@ -14,19 +14,6 @@ When you encounter a problem, the first thing to do is to see if it is
already known. @xref{Trouble}. If it isn't known, then you should
report the problem.
-Reporting a bug may help you by bringing a solution to your problem, or
-it may not. (If it does not, look in the service directory; see
-@ref{Service}.) In any case, the principal function of a bug report is
-to help the entire community by making the next version of GCC work
-better. Bug reports are your contribution to the maintenance of GCC@.
-
-Since the maintainers are very overloaded, we cannot respond to every
-bug report. However, if the bug has not been fixed, we are likely to
-send you a patch and ask you to tell us whether it works.
-
-In order for a bug report to serve its purpose, you must include the
-information that makes for fixing the bug.
-
@menu
* Criteria: Bug Criteria. Have you really found a bug?
* Reporting: Bug Reporting. How to report a bug effectively.
diff --git a/gcc/f/ChangeLog b/gcc/f/ChangeLog
index 2911983e2c4b..c16eb1438d9c 100644
--- a/gcc/f/ChangeLog
+++ b/gcc/f/ChangeLog
@@ -1,3 +1,8 @@
+2003-05-16 Wolfgang Bangerth <bangerth@dealii.org>
+
+ * g77.texi: Remove most of the of the preface of the
+ bugs section.
+
2003-05-15 Wolfgang Bangerth <bangerth@dealii.org>
* g77.texi: Remove most of the bug reporting instructions and
diff --git a/gcc/f/g77.texi b/gcc/f/g77.texi
index bb8db668564a..03f6a6a3afb2 100644
--- a/gcc/f/g77.texi
+++ b/gcc/f/g77.texi
@@ -10422,26 +10422,8 @@ enable/disable/delete/hide intrinsics from the command line?
Your bug reports play an essential role in making GNU Fortran reliable.
When you encounter a problem, the first thing to do is to see if it is
-already known.
-@xref{Trouble}.
-If it isn't known, then you should report the problem.
-
-Reporting a bug might help you by bringing a solution to your problem, or
-it might not.
-(If it does not, look in the service directory; see
-@ref{Service}.)
-In any case, the principal function of a bug report is
-to help the entire community by making the next version of GNU Fortran work
-better.
-Bug reports are your contribution to the maintenance of GNU Fortran.
-
-Since the maintainers are very overloaded, we cannot respond to every
-bug report.
-However, if the bug has not been fixed, we are likely to
-send you a patch and ask you to tell us whether it works.
-
-In order for a bug report to serve its purpose, you must include the
-information that makes for fixing the bug.
+already known. @xref{Trouble}. If it isn't known, then you should
+report the problem.
@menu
* Criteria: Bug Criteria. Have you really found a bug?
--
GitLab