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

diff --git a/PATCHES b/PATCHES
index 361a159134..74a76fdb4d 100644
--- a/PATCHES
+++ b/PATCHES
@@ -1,15 +1,16 @@
-/** @page patchguide OpenOCD Patch Policies
-
-Please mail patches to:
+// This file is part of the Doxygen Developer Manual
+/** @page patchguide Patch Guidelines
 
+Please mail patches to: @par
 	openocd-development@lists.berlios.de
 
 Note that you can't send patches to that list unless
 you're a member, despite what the list info page says.
 
-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.
+@section Patch Guidelines in a Nutshell
+
+Your patches should be against git mainline.  Submit output
+of "git diff"; equivalently, quilt patches are OK.
 
 It should be a "good patch": focus it on a single
 issue, and make it be easily reviewable. Don't make
@@ -31,18 +32,16 @@ in response to feedback.
 Add yourself to the GPL copyright for non-trivial changes.
 
 To create a patch from the command line:
- 
-	svn diff >mypatch.txt
-
-See:
-
-	http://svnbook.red-bean.com/en/1.0/re09.html
+@code 
+	git diff >mypatch.txt
+@endcode
 
-NB! remember to use "svn add" on new files first!
+@section More Information on Patching
 
-	http://svnbook.red-bean.com/en/1.0/re01.html
+The @ref primerpatches provides a more complete guide to creating,
+managing, and contributing patches to the OpenOCD project.
 
-If you have a decent SVN GUI, then that should be
-able to create and apply patches as well...
- 
  */
+/** @file
+This file contains the @ref patchguide page.
+*/