Mention how to cite GDB problem reports.

This commit is contained in:
Andrew Cagney 2001-02-23 22:20:38 +00:00
parent 17fceda3ae
commit 2126d5fbda
3 changed files with 17 additions and 1 deletions

View file

@ -158,3 +158,12 @@ o If ``gdb/gdbarch.sh'' is modified, you don't
``gdbarch.h'' and ``gdbarch.c''. ``gdbarch.h'' and ``gdbarch.c''.
See ``gdb/configure.in'' above. See ``gdb/configure.in'' above.
o When submitting a patch that fixes a bug
in GDB's bug database a brief reference
to the bug can be included in the ChangeLog
vis
* CONTRIBUTE: Mention PR convention. Fix
gdb/4705.

View file

@ -1,9 +1,11 @@
2001-02-23 Andrew Cagney <ac131313@redhat.com> 2001-02-23 Andrew Cagney <ac131313@redhat.com>
* CONTRIBUTE: Document how to cite a problem report.
* TODO: Note need to replace CONTRIBUTE with generated file.
* CONTRIBUTE: Mention that patches do not need to include the * CONTRIBUTE: Mention that patches do not need to include the
generated files gdbarch.h and gdbarch.c. generated files gdbarch.h and gdbarch.c.
2001-02-21 Andrew Cagney <ac131313@redhat.com> 2001-02-21 Andrew Cagney <ac131313@redhat.com>
* value.h (get_saved_register): Move from here. * value.h (get_saved_register): Move from here.

View file

@ -517,6 +517,11 @@ Extreme care is recommeded - perhaps only modify tests that are
exercised by the testsuite (as determined using some type of code exercised by the testsuite (as determined using some type of code
coverage analysis). coverage analysis).
--
Replace the file gdb/CONTRIBUTE with a file that is generated from the
gdb/doc/*.texinfo directory.
-- --
New Features and Fixes New Features and Fixes