You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mason Thomas <ml...@sbcglobal.net> on 2003/03/25 07:17:30 UTC
[PATCH] fixes for Ch.1 of book
Hi, the following patch corrects typos and improves English usage in
chapter 1 of the svn book.
-Mason
log message:
* doc/book/book/ch01.xml: correct typos and usage
Index: doc/book/book/ch01.xml
===================================================================
--- doc/book/book/ch01.xml (revision 5449)
+++ doc/book/book/ch01.xml (working copy)
@@ -22,7 +22,7 @@
<para>Subversion is a free/open-source version control system.
That is, Subversion manages files and directories over time.
- The tree of files are placed into a central
+ A tree of files is placed into a central
<firstterm>repository</firstterm>. The repository is much like
an ordinary file server, except that it remembers every change
ever made to your files and directories. This allows you to
@@ -40,8 +40,8 @@
that are specific to software development (such as natively
understanding programming languages). Subversion, however, is
not one of these systems; it is a general system that can be
- used to manage <emphasis>any</emphasis> sort of collection of
- files, including source code.</para>
+ used to manage <emphasis>any</emphasis> collection of files,
+ including source code.</para>
</sect1>
@@ -56,7 +56,7 @@
a company for commercially supporting and improving the
Concurrent Versions System (CVS). Cyclic made the first public
release of a network-enabled CVS (contributed by Cygnus
- software.) In 1999, Karl Fogel published a book about CVS and
+ software). In 1999, Karl Fogel published a book about CVS and
the open-source development model it enables. Karl and Jim had
long talked about writing a replacement for CVS; Jim had even
drafted a new, theoretical repository design, and had come up
@@ -68,11 +68,11 @@
developed openly under a free license, it quickly attracted a
community of developers.</para>
- <para>The original design team settled on some simple goals. It
- was decided that Subversion should be a functional replacement
- for CVS; it should match CVS's features, preserve the same
+ <para>The original design team settled on some simple goals. They
+ decided that Subversion should be a functional replacement
+ for CVS: It should match CVS's features, preserve the same
development model, but still fix the most obvious flaws. And
- Subversion should be similar enough to CVS such that any CVS
+ Subversion should be similar enough to CVS that any CVS
user could start using it with little effort.</para>
<para>After fourteen months of coding, Subversion became
@@ -84,11 +84,12 @@
very large chunk of the work (it pays the salaries of a few
full-time Subversion developers), the project is still a typical
open-source project, governed by the usual meritocratic rules.
- CollabNet owns the copyright on the code, but that copyright is
- an Apache/BSD-style license which is fully compliant with the
- Debian Free Software Guidelines. In other words, anyone is free
- to download, modify, and redistribute Subversion as he pleases;
- no permission from CollabNet or anyone else is required.</para>
+ CollabNet owns the copyright on the code, but the code is
+ available under an Apache/BSD-style license which is fully
+ compliant with the Debian Free Software Guidelines. In other
+ words, anyone is free to download, modify, and redistribute
+ Subversion as he pleases; no permission from CollabNet or
+ anyone else is required.</para>
</sect1>
@@ -109,14 +110,13 @@
<varlistentry>
<term>Directory versioning</term>
<listitem>
- <para>The Subversion repository doesn't only track the
- history of individual files; instead, it implements a
- <quote>virtual</quote> versioned filesystem that tracks
- changes to trees over time. Files
- <emphasis>and</emphasis> directories are versioned. As a
- result, there are real client-side <command>move</command>
- and <command>copy</command> commands that operate on files
- and directories.</para>
+ <para>CVS only tracks the history of individual files,
+ but Subversion implements a <quote>virtual</quote>
+ versioned filesystem that tracks changes to trees over
+ time. Files <emphasis>and</emphasis> directories are
+ versioned. As a result, there are real client-side
+ <command>move</command> and <command>copy</command>
+ commands that operate on files and directories.</para>
</listitem>
</varlistentry>
@@ -124,7 +124,7 @@
<term>Atomic commits</term>
<listitem>
<para>A commit either goes into the repository completely,
- or not all. This allows developers to commit changes as
+ or not at all. This allows developers to commit changes as
logical <quote>changesets</quote>.</para>
</listitem>
</varlistentry>
@@ -216,21 +216,21 @@
website (<systemitem
class="url">http://subversion.tigris.org</systemitem>) often has
binaries available for download, posted by volunteers. The site
- usually contains graphical installer packages for users for
+ usually contains graphical installer packages for
Microsoft operating systems. If you run a Unix-like operating
system, you can use your system's native package-distribution
system (rpm, deb, ports tree) to get Subversion.</para>
<para>Alternately, you can build Subversion directly from source
code. From the website, you can download the latest source-code
- release. After unpacking it, follow the instructions in INSTALL
- to build it. Note that released source package contains
+ release. After unpacking it, follow the instructions in the INSTALL
+ file to build it. Note that the released source package contains
everything you need to build a commandline-client capable of
talking to a remote repository (in particular, the apr,
- apr-util, and neon libraries.) But Subversion has many other
+ apr-util, and neon libraries). But Subversion has many other
dependencies, such as Berkeley DB and possibly Apache httpd.
If you want to do a <quote>full</quote> build, make sure you
- have all of packages documented in the INSTALL file. If you
+ have all the packages documented in the INSTALL file. If you
plan to work on Subversion itself, you can use your client
program to grab the latest, bleeding-edge source code. This is
documented in <xref linkend="svn-ch-7-sect-6.2" />.</para>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] fixes for Ch.1 of book
Posted by Sander Roobol <ph...@wanadoo.nl>.
Filed as issue #1217.
Sander
On Mon, Mar 24, 2003 at 11:17:30PM -0800, Mason Thomas wrote:
> Hi, the following patch corrects typos and improves English usage in
> chapter 1 of the svn book.
>
> -Mason
>
> [snip]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org