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 <dbrownell@users.sourceforge.net>
This commit is contained in:
parent
e380930478
commit
3ea9e62189
6
BUGS
6
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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue