Here's another update to the bug reporting instructions (identical for
bugreport.texi and g77.texi):
- remove offensive wording (report a bug "may or may not help you" --
what's it good for, then?)
- remove ideological thing about community that is already clearly
stated
in the first sentence of the section (which reads: "Your bug plays an
important role in making GCC reliable.")
- remove whining about overloadedness of maintainers. we should
certainly
strive for at least checking reports!
- remove sentence that states
OK for mainline and branch?
W.
Index: doc/bugreport.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/bugreport.texi,v
retrieving revision 1.5
diff -c -r1.5 bugreport.texi
*** doc/bugreport.texi 15 May 2003 15:01:05 -0000 1.5
--- doc/bugreport.texi 15 May 2003 15:25:59 -0000
***************
*** 14,32 ****
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.
--- 14,19 ----
Index: f/g77.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/f/g77.texi,v
retrieving revision 1.103
diff -c -r1.103 g77.texi
*** f/g77.texi 15 May 2003 15:01:06 -0000 1.103
--- f/g77.texi 15 May 2003 15:25:59 -0000
***************
*** 10422,10447 ****
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.
@menu
* Criteria: Bug Criteria. Have you really found a bug?
--- 10422,10429 ----
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.
@menu
* Criteria: Bug Criteria. Have you really found a bug?