porting: update porting doc

[platform/upstream/gstreamer.git] / README

diff --git a/README b/README
index 7fc0470..1ef13d9 100644 (file)
--- a/README
+++ b/README
@@ -154,7 +154,7 @@ Only in cases where you:
 - want to hack on GStreamer
 - want to verify that a bug has been fixed
 - do not have a sane distribution
-should you choose to build from source tarballs or CVS.
+should you choose to build from source tarballs or git.
 
 Find more information about the various packages at
 http://gstreamer.freedesktop.org/download/
@@ -190,13 +190,13 @@ COMPILING FROM SOURCE TARBALLS
   functionality you're probably looking for by now, so go on and read
   that README.
 
-COMPILING FROM CVS
+COMPILING FROM GIT
 ------------------
 
-When building from CVS sources, you will need to run autogen.sh to generate 
+When building from git sources, you will need to run autogen.sh to generate 
 the build system files.
 
-You will need a set of additional tools typical for building from CVS,
+You will need a set of additional tools typical for building from git,
 including:
 - autoconf
 - automake
@@ -219,8 +219,8 @@ the last passed options as a handy shortcut.  Use it.
 After the autogen.sh stage, you can follow the directions listed in
 "COMPILING FROM SOURCE"
 
-You can also run your whole cvs stack uninstalled.  The script in
-the gstreamer module /docs/faq/gst-uninstalled) is helpful in setting
+You can also run your whole git stack uninstalled.  The script in
+the gstreamer module /scripts/gst-uninstalled) is helpful in setting
 up your environment for this.
 
 PLUG-IN DEPENDENCIES AND LICENSES
@@ -245,4 +245,3 @@ will provide the various codec and other functionality.  The interface
 hopefully is generic enough for various companies (ahem, Apple) to release
 binary codecs for Linux, until such time as they get a clue and release the
 source.
-