[svnbook commit] r3148 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Mon Jun 16 14:11:52 CDT 2008
Author: cmpilato
Date: Mon Jun 16 14:11:52 2008
New Revision: 3148
Log:
* src/en/book/ch00-preface.xml
s/BerkeleyDB/Berkeley DB/. Lose a bunch <quote> tags. Don't refer
to svn:externals as a feature (it's an implementation; "externals
definitions" is the feature).
Modified:
trunk/src/en/book/ch00-preface.xml
Modified: trunk/src/en/book/ch00-preface.xml
==============================================================================
--- trunk/src/en/book/ch00-preface.xml (original)
+++ trunk/src/en/book/ch00-preface.xml Mon Jun 16 14:11:52 2008
@@ -1039,9 +1039,9 @@
<term>Subversion 1.1 (September 2004)</term>
<listitem>
<para>Release 1.1 introduced FSFS, a flat-file repository
- storage option for the repository. While the BerkeleyDB
+ storage option for the repository. While the Berkeley DB
back-end is still widely used and supported, FSFS has
- since become the <quote>default</quote> choice for
+ since become the default choice for
newly-created repositories due to its low barrier to
entry and minimal maintenance requirements. Also in
this release came the ability to put symbolic links
@@ -1054,18 +1054,17 @@
<term>Subversion 1.2 (May 2005)</term>
<listitem>
<para>Release 1.2 introduced the ability to create
- server-side <quote>locks</quote> on files, thus
- serializing commit access to certain resources. While
- Subversion is still a fundamentally concurrent version
- control system, certain types of binary files (art
- assets, for example) cannot be merged together. The
- locking feature fulfills the need to version and protect
- such resources. With locking also came a
- complete <quote>auto-versioning</quote> implementation,
- allowing Subversion repositories to be mounted as
- network folders. Finally, Subversion 1.2 began using a
- new, faster binary-differencing algorithm to compress
- and retrieve old versions of files.</para>
+ server-side locks on files, thus serializing commit
+ access to certain resources. While Subversion is still
+ a fundamentally concurrent version control system,
+ certain types of binary files (art assets, for example)
+ cannot be merged together. The locking feature fulfills
+ the need to version and protect such resources. With
+ locking also came a complete WebDAV auto-versioning
+ implementation, allowing Subversion repositories to be
+ mounted as network folders. Finally, Subversion 1.2
+ began using a new, faster binary-differencing algorithm
+ to compress and retrieve old versions of files.</para>
</listitem>
</varlistentry>
@@ -1086,13 +1085,13 @@
<term>Subversion 1.4 (September 2006)</term>
<listitem>
<para>Release 1.4 introduced a whole new
- tool—<command>svnsync</command>— for doing
+ tool—<command>svnsync</command>—for doing
one-way repository replication over a network. Major
parts of the working copy metadata were revamped to no
longer use XML (resulting in client side speed gains),
- while the BerkeleyDB repository back-end gained the
- ability to automatically <quote>recover</quote> itself
- after a server crash.</para>
+ while the Berkeley DB repository back-end gained the
+ ability to automatically recover itself after a server
+ crash.</para>
</listitem>
</varlistentry>
@@ -1109,8 +1108,7 @@
user-focused features, such as interactive resolution of
file conflicts, partial checkouts, client side
management of changelists, powerful new syntax for
- the <literal>svn:externals</literal> feature, and SASL
- authentication support for
+ externals definitions, and SASL authentication support for
the <command>svnserve</command> server.</para>
</listitem>
</varlistentry>
More information about the svnbook-dev
mailing list