[svnbook commit] r2693 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Fri Feb 23 01:10:39 CST 2007
Author: cmpilato
Date: Fri Feb 23 01:10:38 2007
New Revision: 2693
Modified:
trunk/src/en/book/ch-basic-usage.xml
trunk/src/en/book/ch-server-configuration.xml
Log:
* src/en/book/ch-server-configuration.xml
* src/en/book/ch-basic-usage.xml
Commit up some hopefully non-controversial mostly-formatting tweaks.
Modified: trunk/src/en/book/ch-basic-usage.xml
==============================================================================
--- trunk/src/en/book/ch-basic-usage.xml (original)
+++ trunk/src/en/book/ch-basic-usage.xml Fri Feb 23 01:10:38 2007
@@ -28,10 +28,10 @@
<para>Before reading on, here is the most important command you'll
ever need when using Subversion: <command>svn help</command>.
- The Subversion command-line client is
- self-documenting—at any time, a quick <command>svn help
- <subcommand></command> will describe the syntax, options,
- and behavior of the <command>subcommand</command>.</para>
+ The Subversion command-line client is self-documenting—at
+ any time, a quick <command>svn help
+ <replaceable>SUBCOMMAND</replaceable></command> will describe
+ the syntax, options, and behavior of the subcommand.</para>
</sect1>
@@ -42,8 +42,8 @@
<title>Getting Data into your Repository</title>
<para>There are two ways to get new files into your Subversion
- repository: <command>svn import</command> and <command>svn
- add</command>.</para>
+ repository: <command>svn import</command> and <command>svn
+ add</command>.</para>
<!-- =============================================================== -->
<sect2 id="svn.tour.importing.import">
Modified: trunk/src/en/book/ch-server-configuration.xml
==============================================================================
--- trunk/src/en/book/ch-server-configuration.xml (original)
+++ trunk/src/en/book/ch-server-configuration.xml Fri Feb 23 01:10:38 2007
@@ -3,12 +3,12 @@
<para>A Subversion repository can be accessed simultaneously by
clients running on the same machine on which the repository
- resides using the <literal>file:///</literal> method. But the
+ resides using the <literal>file://</literal> method. But the
typical Subversion setup involves a single server machine being
accessed from clients on computers all over the office—or,
perhaps, all over the world.</para>
- <para>This section describes how to get your Subversion repository
+ <para>This chapter describes how to get your Subversion repository
exposed outside its host machine for use by remote clients. We
will cover Subversion's currently available server mechanisms,
discussing the configuration and use of each. After reading
@@ -30,7 +30,7 @@
access</quote> API allows programmers to write plugins that
speak relevant network protocols. In theory, Subversion can use
an infinite number of network implementations. In practice,
- there are only two servers at the time of writing.</para>
+ there are only two servers at the time of this writing.</para>
<para>Apache is an extremely popular webserver; using the
<command>mod_dav_svn</command> module, Apache can access a
@@ -123,18 +123,13 @@
<title>The Apache HTTP Server</title>
- <variablelist>
-
- <varlistentry>
- <term>How it works:</term>
- <listitem>
- <para>Install and configure a standard Apache 2.0
- server, then activate a special subversion-server module.
- Clients speak to server via HTTP or HTTPS, using the WebDAV
- protocol.</para>
- </listitem>
- </varlistentry>
+ <para>The Apache HTTP Server is a well-establish, full-featured
+ web server program. But when you extend this server with the
+ mod_dav_svn Subversion server module, the Apache HTTP Server
+ becomes a Subversion server, too. Clients speak to server via
+ HTTP or HTTPS, using the WebDAV protocol.</para>
+ <variablelist>
<varlistentry>
<term>Why you might want to use it:</term>
<listitem>
@@ -191,19 +186,13 @@
<title>The <command>svnserve</command> Server</title>
- <variablelist>
-
- <varlistentry>
- <term>How it works:</term>
- <listitem>
- <para>A lightweight serve process which can run either as
- a persistent daemon, or as something automatically
- launched by inetd when necessary. Clients authenticate
- via CRAM-MD5 algorithm and speak a custom network
- protocol.</para>
- </listitem>
- </varlistentry>
+ <para><command>svnserve</command> is a lightweight server
+ process which can run either as a persistent daemon, or as
+ something automatically launched by inetd when necessary.
+ Clients authenticate via the CRAM-MD5 algorithm and speak a
+ network protocol that is custom to Subversion.</para>
+ <variablelist>
<varlistentry>
<term>Why you might want to use it:</term>
<listitem>
@@ -254,22 +243,18 @@
<title><command>svnserve</command> over SSH</title>
- <variablelist>
-
- <varlistentry>
- <term>How it works:</term>
- <listitem>
- <para> Each client uses an existing SSH (system) account
- to spawn a temporary <command>svnserve</command> process
- (running as themselves) on the server machine. The
- <command>svnserve</command> process accesses the
- repository, communicates with the client over the SSH
- tunnel, then dies when the SSH connection is closed.
- (There is no long-running <command>svnserve</command>
- process.)</para>
- </listitem>
- </varlistentry>
+ <para><command>svnserve</command> can be invoked via SSH to
+ handle Subversion client communication tunneled across that
+ protocol. Each Subversion client uses an existing
+ SSH-accessed system account to spawn a temporary
+ <command>svnserve</command> process (running as themselves) on
+ the server machine. The <command>svnserve</command> process
+ accesses the repository, communicates with the client over the
+ SSH tunnel, then dies when the SSH connection is closed.
+ (There is no long-running <command>svnserve</command>
+ process.)</para>
+ <variablelist>
<varlistentry>
<term>Why you might want to use it:</term>
<listitem>
More information about the svnbook-dev
mailing list