X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=PATCHES;h=ed980b856817ff09ae352024e091b3979954adee;hb=a49faa206d0c67b84b1fa364112775c1c80fa9b5;hp=361a1591343ee2b3aedaf3a6dc3c06f212f45a5b;hpb=b3a8f5dc2a32f62ec7f2199461c62df9becaf7f6;p=openocd.git

diff --git a/PATCHES b/PATCHES
index 361a159134..ed980b8568 100644
--- a/PATCHES
+++ b/PATCHES
@@ -1,4 +1,4 @@
-/** @page patchguide OpenOCD Patch Policies
+/** @page patchguide Patch Guidelines
 
 Please mail patches to:
 
@@ -7,6 +7,8 @@ Please mail patches to:
 Note that you can't send patches to that list unless
 you're a member, despite what the list info page says.
 
+@section Patch Guidelines in a Nutshell
+
 The patch should be against svn trunk using an SVN
 diff. If you use git-svn, a git diff or patch is OK
 too; likewise a quilt patch, if you use quilt.
@@ -31,18 +33,25 @@ in response to feedback.
 Add yourself to the GPL copyright for non-trivial changes.
 
 To create a patch from the command line:
- 
+@code 
 	svn diff >mypatch.txt
+@endcode
 
-See:
-
+See: @par
 	http://svnbook.red-bean.com/en/1.0/re09.html
 
-NB! remember to use "svn add" on new files first!
-
+Remember to use "svn add" on new files first: @par
 	http://svnbook.red-bean.com/en/1.0/re01.html
 
 If you have a decent SVN GUI, then that should be
 able to create and apply patches as well...
  
+@section More Information on Patching
+
+The @ref primerpatches provides a more complete guide to creating,
+managing, and contributing patches to the OpenOCD project.
+
  */
+/** @file
+This file contains the @ref patchguide page.
+*/