summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-09-03 19:30:57 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-09-03 19:30:57 +0000
commita95a5af50a1f7e845e0ef53aa3aa4660798af702 (patch)
tree9702130b56aaf6e25e245e7388b78742a26f4997 /DOCS
parentae365e2f749bf5747e95cff2cbd125dd31c3f6b9 (diff)
downloadmpv-a95a5af50a1f7e845e0ef53aa3aa4660798af702.tar.bz2
mpv-a95a5af50a1f7e845e0ef53aa3aa4660798af702.tar.xz
Remove outdated references to CVS.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@19663 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/tech/translations.txt17
1 files changed, 9 insertions, 8 deletions
diff --git a/DOCS/tech/translations.txt b/DOCS/tech/translations.txt
index defbb454a9..d01827baed 100644
--- a/DOCS/tech/translations.txt
+++ b/DOCS/tech/translations.txt
@@ -11,9 +11,9 @@ maintain a new documentation translation.
Documentation related discussions happen on the MPlayer-DOCS mailing list,
while documentation translation related discussions happen on the
MPlayer-translations mailing list. If you want to maintain a translation
-you should subscribe to both, as the English documentation CVS changelogs,
-which you need to keep the translation up to date, are sent to MPlayer-DOCS.
-You can subscribe here:
+you should subscribe to both, as the English documentation Subversion
+changelogs, which you need to keep the translation up to date, are sent
+to MPlayer-DOCS. You can subscribe here:
http://mplayerhq.hu/mailman/listinfo/mplayer-docs
http://mplayerhq.hu/mailman/listinfo/mplayer-translations
@@ -30,7 +30,7 @@ order of importance:
Please note that only doing 1) or 1) + 2) is perfectly fine.
-You can find the latest versions of the help_mp-XX.h files in CVS or
+You can find the latest versions of the help_mp-XX.h files in Subversion or
here:
http://svn.mplayerhq.hu/mplayer/trunk/help/
@@ -76,7 +76,8 @@ incomplete, please let us know, we'll fix it. Patches are more than welcome,
of course. Do not, however, change the translation first, please get your
update into the English version first.
-If you have CVS access and commit a translation update file, use something like
-"synced with 1.XXX" as first line of the commit message so that it is possible
-to tell with a glance at the cvs log or viewcvs if the translation is outdated
-and which revision of the English master file it is equivalent to.
+If you have Subversion write access and commit a translation update file,
+use something like "synced with 1.XXX" as first line of the commit message
+so that it is possible to tell with a glance at the cvs log or viewcvs if
+the translation is outdated and which revision of the English master file
+it is equivalent to.