[fyi] document ``Fix gdb/4705.''
Andrew Cagney
ac131313@cygnus.com
Fri Feb 23 14:20:00 GMT 2001
FYI,
Following up on the discussion on gdb@ I've checked in the attatched.
There isn't any need to explain a bug in a ChangeLog entry however a
brief reference like ``Fix gdb/4705'' wouldn't hurt.
Andrew
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.
Index: CONTRIBUTE
===================================================================
RCS file: /cvs/src/src/gdb/CONTRIBUTE,v
retrieving revision 1.3
diff -p -r1.3 CONTRIBUTE
*** CONTRIBUTE 2001/02/23 22:09:30 1.3
--- CONTRIBUTE 2001/02/23 22:15:32
*************** o If ``gdb/gdbarch.sh'' is modified, you
*** 158,160 ****
--- 158,169 ----
``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.
Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.60
diff -p -r1.60 TODO
*** TODO 2001/02/19 23:20:54 1.60
--- TODO 2001/02/23 22:15:37
*************** coverage analysis).
*** 519,524 ****
--- 519,529 ----
--
+ Replace the file gdb/CONTRIBUTE with a file that is generated from the
+ gdb/doc/*.texinfo directory.
+
+ --
+
New Features and Fixes
======================
More information about the Gdb-patches
mailing list