Mention how to cite GDB problem reports.

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index 91e3634d4fb2138e351486ccf6c2f2e49e29d1e8..f7f81c7c9f0e533b2b9603169e02bdbb7f1427a2 100644 (file)
--- a/gdb/CONTRIBUTE
+++ b/gdb/CONTRIBUTE
@@ -158,3 +158,12 @@ o  If ``gdb/gdbarch.sh'' is modified, you don't
        ``gdbarch.h'' and ``gdbarch.c''.
 
        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.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index ff24823757ea7325b174fd1bc20efe05a6f0a9be..c82f452bd0c480491b0559b9a9caf94718108350 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,9 +1,11 @@
 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
        generated files gdbarch.h and gdbarch.c.
        
-       
 2001-02-21  Andrew Cagney  <ac131313@redhat.com>
 
        * value.h (get_saved_register): Move from here.

diff --git a/gdb/TODO b/gdb/TODO
index cebae792fc8df79ceee34eb9d66cfa0a405b9081..5019d318a62f8b8c7a0169fd9b917029393b7b89 100644 (file)
--- a/gdb/TODO
+++ b/gdb/TODO
@@ -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
 coverage analysis).
 
+--
+
+Replace the file gdb/CONTRIBUTE with a file that is generated from the
+gdb/doc/*.texinfo directory.
+
 --
 
                        New Features and Fixes