# HG changeset patch
# User diego
# Date 1149761344 0
# Node ID 80df1b8c375956bdcb15e344d91ee8d8dc3e5f58
# Parent  8c6bdea1585c0991de755e9e7be79fd4628f608c
s/CVS/Subversion/

diff -r 8c6bdea1585c -r 80df1b8c3759 DOCS/tech/patches.txt
--- a/DOCS/tech/patches.txt	Thu Jun 08 10:07:12 2006 +0000
+++ b/DOCS/tech/patches.txt	Thu Jun 08 10:09:04 2006 +0000
@@ -12,11 +12,11 @@
     soon as one of the files changes, your version becomes harder to apply,
     thus reducing its chances of being accepted.
 
- 1. Always make patches for the CVS version. The README describes how to check
-    out CVS and daily CVS snapshots are available from our download page.
-    We do not accept patches for releases or outdated CVS versions.
+ 1. Always make patches for Subversion HEAD. The README describes how to check
+    out Subversion and daily snapshots are available from our download page.
+    We do not accept patches for releases or outdated Subversion revisions.
 
- 2. Make unified diffs ('diff -Naur' or 'cvs diff -u'). Unified diffs can be
+ 2. Make unified diffs ('svn diff' or 'diff -Naur'). Unified diffs can be
     applied easily with 'patch'. This is much harder with other diff types.
     Besides, unified diffs are more readable and thus easier to review.
 
@@ -91,9 +91,9 @@
     reminders must be sent as replies to the original patch to preserve proper
     mail threading.
 
-11. Do not immediately ask for CVS write access. If you have contributed one or
-    more nice, acceptable patches and they need maintaining or you want to
-    be an MPlayer developer, you'll get CVS write access.
+11. Do not immediately ask for Subversion write access. If you have contributed
+    one or more nice, acceptable patches and they need maintaining or you want
+    to be an MPlayer developer, you'll get Subversion write access.
 
 12. For consistency reasons, all option names must use '-' instead of '_'.