docs/en wine-faq.sgml

[Dimi Paun]

ChangeSet ID:	1156506455193357847006158
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	dimi at sc8-pr-cvs9.sourceforge.net	2006/08/25 04:47:35

Modified files:
	en             : wine-faq.sgml 

Log message:
	Mike McCormack <mike at codeweavers.com>
	Update the FAQ to reference Git.


Old revision  New revision  Changes     Path
 1.18          1.19          +15 -59     docs/en/wine-faq.sgml

Index: docs/en/wine-faq.sgml
diff -u -p docs/en/wine-faq.sgml:1.18 docs/en/wine-faq.sgml:1.19
--- docs/en/wine-faq.sgml	25 Aug 2006 11:47:35 -0000
+++ /dev/null	25 Aug 2006 11:47:35 -0000
@@ -395,8 +395,8 @@ cvs -z3 -d:pserver:anonymous at wine.cvs.so
           you are current to the previous version, you can download and apply 
           just the current patch file rather than the entire new distribution.
           The patch file names follow the same conventions as the monthly 
-          distribution. <ulink url="http://www.winehq.org/site/cvs">
-          Read-only CVS</ulink> access is also available.
+          distribution. <ulink url="http://www.winehq.org/site/git">
+          Read-only GIT</ulink> access is also available.
         </para>
       </answer>
       </qandaentry>
@@ -721,7 +721,7 @@ cvs -z3 -d:pserver:anonymous at wine.cvs.so
         <para>
           Wine is getting to be quite large, and building from scratch takes a
           lot of processing. As of September 2005, compile times were around 15
-          minutes on a Intel 3.8GHz Laptop with 1 GB of RAM. If you have a CVS copy of wine, 
+          minutes on a Intel 3.8GHz Laptop with 1 GB of RAM. If you have a Git copy of wine, 
 	  you may not need to rebuild every thing each update.
         </para>
       </answer>
@@ -919,45 +919,26 @@ cvs -z3 -d:pserver:anonymous at wine.cvs.so
       </qandaentry>
 
       <qandaentry>
-      <question id="Is-there-a-CVS-tree">
-        <para>Is there a CVS tree?</para>
+      <question id="Is-there-a-Git-tree">
+        <para>Is there a Git tree?</para>
       </question>
       <answer>
         <para>
-          Current Wine sources are also available via anonymous client/server
-          CVS. You will need CVS 1.9 or above. If you are coming from behind a
-          firewall, you will either need a hole in the firewall for the CVS
-          port (2401) or use SOCKS.
+          Current Wine sources are also available via Git
+          You will need Git 1.3.1 or above. If you are coming from behind a
+          firewall, use the http:// protocol.
         </para>
         <para>
-          To login to the CVS tree, do
+          To clone out the entire Wine source tree (which may be slow), use
         </para>
         <screen>
-export CVSROOT=:pserver:cvs at cvs.winehq.org/home/wine
-cvs login
+git clone git://source.winehq.org/git/wine.git wine
         </screen>
         <para>
-          Use "cvs" as the password (without the quotes). Note that 
-          <filename>/home/wine</filename> is a path on the server, not on your
-          machine. To check out the entire Wine source tree (which may be 
-          slow), use
-        </para>
-        <screen>
-cvs -z 3 checkout wine 
-        </screen>
-        <para>
-          or if you just want a subtree, or individual file, you can do that 
-          too with
-        </para>
-        <screen>
-cvs -z 3 checkout wine/ANNOUNCE 
-        </screen>
-        <para>
-          Be aware, though, that getting the entire Wine source tree via CVS
-          is pretty slow, especially compared to getting Wine from an FTP 
-          mirror near you. For a CVS mirror list, see 
-          <ulink url="http://www.winehq.org/site/cvs#cvsservers">
-          http://www.winehq.org/site/cvs#cvsservers</ulink>
+          Be aware, though, that the initial clone of the entire Wine source
+          tree via Git is pretty slow, especially compared to getting Wine from
+          an FTP mirror near you.  Updating to your cloned repository is
+          reasonably fast, however.
         </para>
         <para>
           Patch files are also available, so that you don't have to download,
@@ -991,31 +972,6 @@ gunzip -c patch-file | patch -p1 
         </para>
       </answer>
       </qandaentry>
-
-      <qandaentry>
-      <question id="Can-I-get-Wine-using-cvsup">
-        <para>Can I get Wine using cvsup?</para>
-      </question>
-      <answer>
-        <para>
-          The CVS mirrors don't offer cvsup support yet, but the main server
-          does. Use a <filename>wine.sup</filename> file of:
-        </para>
-        <screen>
-*default host=cvs.winehq.org
-*default base=/cvs
-*default prefix=/cvs/wine
-*default release=wine
-*default delete 
-
-# If your network link is a T1 or faster, comment out the following line.
-#*default compress 
-
-*default use-rel-suffix 
-wine 
-        </screen>
-     </answer>
-     </qandaentry>
     </qandadiv>
 
     <qandadiv id="Installing-And-Configuring-Wine">
@@ -1581,7 +1537,7 @@ export PATH=$PATH:/path/to/wine/binary 
       <answer>
         <para>
           If you can program C, that's a good start. Download the sources via
-          (<ulink url="http://www.winehq.org/site/cvs">CVS,</ulink>)
+          (<ulink url="http://www.winehq.org/site/git">Git,</ulink>)
           subscribe to the mailing lists, look around the source, and
           pay attention to the comp.emulators.ms-windows.wine newsgroup
           and the mailing lists (<ulink