INN commit: trunk/doc (FAQ)

[INN Commit]

    Date: Saturday, December 13, 2008 @ 19:03:29
  Author: eagle
Revision: 8219

Change multiple references from CVS to Subversion.

Modified:
  trunk/doc/FAQ

-----+
 FAQ |   23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

Modified: FAQ
===================================================================
--- FAQ	2008-12-07 11:01:43 UTC (rev 8218)
+++ FAQ	2008-12-14 03:03:29 UTC (rev 8219)
@@ -159,7 +159,7 @@
 (particularly of security holes), the original INN Usenix paper.
 
 There is also a snapshots subdirectory, in which you will find daily
-snapshots of the INN CVS repository for the last seven days.  The
+snapshots of the INN Subversion repository for the last seven days.  The
 snapshots with STABLE in the name are the latest versions of the STABLE
 branch and may have some additional bug fixes over the current released
 version.  The snapshots with CURRENT in the name are of the current
@@ -253,7 +253,7 @@
     posting).
 
 inn-committers at isc.org
-    CVS commit messages for INN are sent to this list (no posting
+    Subversion commit messages for INN are sent to this list (no posting
     allowed).
 
 inn-bugs at isc.org
@@ -320,9 +320,8 @@
     can learn more about the ISC's goals and accomplishments from the web
     page at <http://www.isc.org/>.
 
-The ISC provides ftp and web space, CVS server access for developers, and
-mailing lists and archives.  Donations to help support all of that are
-greatly appreciated.
+The ISC provides ftp and web space and mailing lists and archives.
+Donations to help support all of that are greatly appreciated.
 
 ------------------------------
 
@@ -332,12 +331,16 @@
 takes place.  The traffic isn't that high.
 
 Next, download a snapshot of the INN CURRENT branch as described above so
-that you have a relatively current source base to work from.  You may also
-want to try configuring CVSup or some other update mechanism so that you
-can get the latest version directly out of CVS, or you can just use the
-nightly snapshots if you wish.  Read the HACKING file at the top of the
-INN source tree for some general information and tips for working on INN.
+that you have a relatively current source base to work from.  You may want
+to check out the current source from Subversion; just point a Subversion
+client at:
 
+    http://inn.eyrie.org/svn/
+
+This repository is a read-only mirror that can lag up to an hour behind
+the working repository.  Read the HACKING file at the top of the INN
+source tree for some general information and tips for working on INN.
+
 Then pick something that looks interesting to you, mention what you're
 doing on inn-workers if it's likely to affect other parts of the
 development, and have at it!  The TODO file in the CURRENT tree has a