X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=PATCHES;h=32f1bda5f070f0bee4b6a55f4b0d8a95b596a147;hb=03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8;hp=74fd696760e4631bf8d1f51f4c2f98f4108f20c7;hpb=cdc33b38088e6435393b86808b6833d09ea4aa73;p=openocd

diff --git a/PATCHES b/PATCHES
index 74fd6967..32f1bda5 100644
--- a/PATCHES
+++ b/PATCHES
@@ -9,9 +9,8 @@ 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.
+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
@@ -34,18 +33,9 @@ Add yourself to the GPL copyright for non-trivial changes.
 
 To create a patch from the command line:
 @code 
-	svn diff >mypatch.txt
+	git diff >mypatch.txt
 @endcode
 
-See: @par
-	http://svnbook.red-bean.com/en/1.0/re09.html
-
-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,