diff options
author | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2006-06-08 10:09:04 +0000 |
---|---|---|
committer | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2006-06-08 10:09:04 +0000 |
commit | 260979f21b67acadf12eeaf10d240e046a95e2aa (patch) | |
tree | 6867d23ed2f97a4a127cbc26eeed9c02b2c95e3e /DOCS/tech | |
parent | 3f2e6f3a2fdee08faa58c7f99106e72e1022427a (diff) | |
download | mpv-260979f21b67acadf12eeaf10d240e046a95e2aa.tar.bz2 mpv-260979f21b67acadf12eeaf10d240e046a95e2aa.tar.xz |
s/CVS/Subversion/
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@18647 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/tech')
-rw-r--r-- | DOCS/tech/patches.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt index cdc931410e..1e818d8aa7 100644 --- a/DOCS/tech/patches.txt +++ b/DOCS/tech/patches.txt @@ -12,11 +12,11 @@ that your patch will be included. 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 @@ that your patch will be included. 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 '_'. |