[svnbook commit] r2835 - trunk/src/en/book

[sussman]

Author: sussman
Date: Sun Aug 12 15:45:18 2007
New Revision: 2835

Log:
Updates to Appendix B, for the svn 1.4 book.

* src/en/book/appab-svn-for-cvs-users.html
    - Minor rewordings.
    - Link to the reference section on 'svn status' codes.
    - Don't offer many repository converter tools;  take a stand and
      just recommend cvs2svn.  Duh.





Modified:
   trunk/src/en/book/appb-svn-for-cvs-users.xml

Modified: trunk/src/en/book/appb-svn-for-cvs-users.xml
==============================================================================
--- trunk/src/en/book/appb-svn-for-cvs-users.xml	(original)
+++ trunk/src/en/book/appb-svn-for-cvs-users.xml	Sun Aug 12 15:45:18 2007
@@ -285,8 +285,10 @@
            paragraph *is* about -u, not -v, my patch concentrated on
            that. -->
 
-      <para>Lastly, here's a quick summary of the most common status codes that
-        you may see:</para>
+      <para>At this point, you should take a quick look at the list of
+        all possible status codes in
+        <xref linkend="svn.ref.svn.c.status"/>.  Here are a few of the
+        more common status codes you'll see:</para>
 
       <screen>
 A    Resource is scheduled for Addition
@@ -476,9 +478,9 @@
     <title>Authentication</title>
 
     <para>With CVS's pserver, you are required to <quote>login</quote>
-      to the server before any read or write operation—you even
-      have to login for anonymous operations.  With a Subversion
-      repository using Apache <command>httpd</command> or
+      to the server before any read or write operation—you
+      sometimes even have to login for anonymous operations.  With a
+      Subversion repository using Apache <command>httpd</command> or
       <command>svnserve</command> as the server, you don't provide
       any authentication credentials at the outset—if an
       operation that you perform requires authentication, the server
@@ -522,21 +524,15 @@
       claiming to at least partially support the ability to convert
       existing CVS repositories into Subversion ones.</para>
 
-    <para>One such tool is cvs2svn
-      (<ulink url="http://cvs2svn.tigris.org/"/>), a Python script
-      originally created by members of Subversion's own development
-      community.  Others include Lev Serebryakov's RefineCVS
-      (<ulink url="http://lev.serebryakov.spb.ru/refinecvs/"/>).
-      These tools have various levels of completeness, and may make
-      entirely different decisions about how to handle your CVS
-      repository history.  Whichever tool you decide to use, be sure
-      to perform as much verification as you can stand on the
-      conversion results—after all, you've worked hard to build
-      that history!</para>
-
-    <para>For an updated collection of links to known converter tools,
-      visit the Links page of the Subversion website
-      (<ulink url="http://subversion.tigris.org/project_links.html"/>).</para>
+    <para>The most popular (and likely the most mature) conversion
+      tool is cvs2svn (<ulink url="http://cvs2svn.tigris.org/"/>), a
+      Python script originally created by members of Subversion's own
+      development community.  This tool is meant to run exactly
+      once:  it scans your CVS repository multiple times and attempts
+      to deduce commits, branches, and tags as best it can.  When it
+      finishes, the result is a either a Subversion repository or a
+      portable Subversion dumpfile representing your code's history.
+      See the website for detailed instructions and caveats.</para>
 
   </sect1>