From 3ea9e62189205cfa84a04ec6955aaf1f5184a937 Mon Sep 17 00:00:00 2001 From: David Brownell Date: Thu, 4 Feb 2010 11:10:15 -0800 Subject: [PATCH] Documentation: mention bug database Have the User's Guide and BUG handling notes both reference the fact that we now have a bug database at SourceForge. Signed-off-by: David Brownell --- BUGS | 6 ++++++ doc/openocd.texi | 9 ++++++++- 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/BUGS b/BUGS index 36a7da376..5e640e758 100644 --- a/BUGS +++ b/BUGS @@ -6,6 +6,12 @@ posting a message with your report: openocd-development@lists.berlios.de +Also, please check the Trac bug database to see if a ticket for +the bug has already been opened. You might be asked to open +such a ticket, or to update an existing ticket with more data. + + https://sourceforge.net/apps/trac/openocd/ + To minimize work for OpenOCD developers, you should try to include all of the information listed below. If you feel that some of the items below are unnecessary for a clear bug report, you may leave diff --git a/doc/openocd.texi b/doc/openocd.texi index 957c79c52..d4e60a804 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -60,7 +60,7 @@ Free Documentation License''. @menu * About:: About OpenOCD -* Developers:: OpenOCD Developers +* Developers:: OpenOCD Developer Resources * JTAG Hardware Dongles:: JTAG Hardware Dongles * About JIM-Tcl:: About JIM-Tcl * Running:: Running OpenOCD @@ -226,6 +226,13 @@ Discuss and submit patches to this list. The @file{PATCHES.txt} file contains basic information about how to prepare patches. +@section OpenOCD Bug Database + +During the 0.4.x release cycle the OpenOCD project team began +using Trac for its bug database: + +@uref{https://sourceforge.net/apps/trac/openocd} + @node JTAG Hardware Dongles @chapter JTAG Hardware Dongles -- 2.11.4.GIT