aboutsummaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authorAntonio Borneo <borneo.antonio@gmail.com>2009-12-30 07:48:49 +0800
committerDavid Brownell <dbrownell@users.sourceforge.net>2009-12-30 11:51:29 -0800
commit7c5acf8660ddfce4746152e03749b699532f513f (patch)
tree3542639833cbf6b00a84ff606e592faa3ca7d332 /BUGS
parent17fb7ead4b901f10c01c0824f594d91775b012b3 (diff)
downloadriscv-openocd-7c5acf8660ddfce4746152e03749b699532f513f.zip
riscv-openocd-7c5acf8660ddfce4746152e03749b699532f513f.tar.gz
riscv-openocd-7c5acf8660ddfce4746152e03749b699532f513f.tar.bz2
whitespace cleanup, mostly for docs
Remove useless space/tab at end of lines. Remove spaces in indentation and replace with tab. Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS4
1 files changed, 2 insertions, 2 deletions
diff --git a/BUGS b/BUGS
index 6967525..961b339 100644
--- a/BUGS
+++ b/BUGS
@@ -22,7 +22,7 @@ that may be important.
- If the report is for a regression:
- Include logs for both working and broken versions.
- Find the precise version that caused the regression by binary search.
- You can use "git bisect" to expedite this binary search:
+ You can use "git bisect" to expedite this binary search:
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
If possible, please develop and attach a patch that helps to expose or
@@ -36,7 +36,7 @@ in total.
@section bugscrashdump Obtaining Crash Backtraces
If OpenOCD is crashing, there are two very effective things you can do to
-improve your chances of getting help on the development mailing list.
+improve your chances of getting help on the development mailing list.
Try to reproduce the problem using the dummy JTAG interface to allow other developers to replicate
your problem robustly and use GDB to get a trace:@par