Index: doc/book/book/ch08.xml =================================================================== --- doc/book/book/ch08.xml (revision 9133) +++ doc/book/book/ch08.xml (working copy) @@ -513,16 +513,18 @@ $ svn --version -svn, version 0.25.0 (dev build) - compiled Jul 18 2003, 16:25:59 - -Copyright (C) 2000-2003 CollabNet. +svn, version 1.0.1 (r9023) + compiled Mar 17 2004, 09:31:13 + +Copyright (C) 2000-2004 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ - +This product includes software developed by CollabNet (http://www.Collab.Net/). + The following repository access (RA) modules are available: - + * ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol. - handles 'http' schema + - handles 'https' schema * ra_local : Module for accessing a repository on local disk. - handles 'file' schema * ra_svn : Module for accessing a repository using the svn network protocol. @@ -1539,8 +1541,8 @@ distribution (if such is available for your platform), or downloading the latest source tarball and building your own Subversion client. If you build from source, make sure to - read the INSTALL file in the top level of the source tree for - instructions. + read the INSTALL file in the top level of + the source tree for instructions. After you have a working Subversion client, you are now poised to checkout a working copy of the Subversion source @@ -1572,8 +1574,8 @@ directory, though, after this operation completes, you will now have the Subversion source code. Of course, you will still need to fetch a few helper libraries (apr, apr-util, - etc.)—see the INSTALL file in the top level of the - working copy for details. + etc.)—see the INSTALL file in the + top level of the working copy for details. @@ -1583,8 +1585,9 @@ Now that you have a working copy containing the latest Subversion source code, you will most certainly want to take a - cruise through the HACKING file in that working copy's - top-level directory. The HACKING file contains general + cruise through the HACKING file in that + working copy's top-level directory. The + HACKING file contains general instructions for contributing to Subversion, including how to properly format your source code for consistency with the rest of the codebase, how to describe your proposed changes with an @@ -1650,9 +1653,9 @@ allows you to specify that a given test is expected to fail (called an XFAIL), and so long as Subversion fails in the way that was expected, a test result - of XFAIL itself is considered a success. Ultimately, the - better the test suite, the less time wasted on diagnosing - potentially obscure regression bugs. + of XFAIL itself is considered a success. + Ultimately, the better the test suite, the less time wasted on + diagnosing potentially obscure regression bugs.