procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* doc/bugreport.texi, f/g77.texi: Remove most of the preface of the bug reporting section.

Browse source 
From-SVN: r66863
This commit is contained in:
Wolfgang Bangerth 2003-05-16 09:02:19 -06:00 • committed by Wolfgang Bangerth
parent b80c098742
commit 674e9baac9
4 changed files with 12 additions and 33 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/ChangeLog
View file

@ -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

13
gcc/doc/bugreport.texi
View file

@ -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.

5
gcc/f/ChangeLog
View file

@ -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

22
gcc/f/g77.texi
View file

@ -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?