-Please report bugs by posting a message to \r
-\r
-openocd-development@lists.berlios.de.\r
-\r
-To minimize work for OpenOCD developers, you can include\r
-all the information below. If you feel that some of the\r
-items below are unecessary for a clear bug report, you\r
-leave them out.\r
-\r
-\r
-- Target PCB/board description\r
-- Config scripts\r
-- OpenOCD command line\r
-- List of commands issued or GDB operations performed\r
-- Expected result\r
-- Actual result\r
-- debug_level 3 logs\r
-- If this is a regression, include logs for working and broken\r
-version\r
-- If this is a regression, please find out the precise version\r
-that caused the regression. This can be done via a binary\r
-search. E.g. if version 550 worked and 600 failed, then try\r
-575, etc.\r
-\r
-\r
-attach files directly to the posting. The mailing list knows to \r
-transform attachments to links so you will not be bloating anyones\r
+Please report bugs by posting a message to
+
+openocd-development@lists.berlios.de.
+
+To minimize work for OpenOCD developers, you can include
+all the information below. If you feel that some of the
+items below are unecessary for a clear bug report, you
+leave them out.
+
+
+- Target PCB/board description
+- Config scripts
+- OpenOCD command line
+- List of commands issued or GDB operations performed
+- Expected result
+- Actual result
+- debug_level 3 logs
+- If this is a regression, include logs for working and broken
+version
+- If this is a regression, please find out the precise version
+that caused the regression. This can be done via a binary
+search. E.g. if version 550 worked and 600 failed, then try
+575, etc.
+
+
+attach files directly to the posting. The mailing list knows to
+transform attachments to links so you will not be bloating anyones
mail box. Keep attachments to <100kBytes.
\ No newline at end of file