[svnbook] r4392 committed - * en/book/ch00-preface.xml...
svnbook at googlecode.com
svnbook at googlecode.com
Mon Feb 4 09:57:02 CST 2013
Revision: 4392
Author: cmpilato at gmail.com
Date: Mon Feb 4 07:56:53 2013
Log: * en/book/ch00-preface.xml
(svn.intro.righttool): Rework the "comparison" paragraph to point
out why the DVCS tools do well what they do well, and try to note
that centralized systems allow mixed-rev working copies without
using the terms "mixed-rev" or "working copies" (which aren't yet
introduced). Sheesh.
Suggested by: danielsh
http://code.google.com/p/svnbook/source/detail?r=4392
Modified:
/trunk/en/book/ch00-preface.xml
=======================================
--- /trunk/en/book/ch00-preface.xml Fri Feb 1 10:39:22 2013
+++ /trunk/en/book/ch00-preface.xml Mon Feb 4 07:56:53 2013
@@ -204,18 +204,22 @@
<para>There are pros and cons to each version control approach.
Perhaps the two biggest benefits delivered by the DVCS tools
- are incredible performance for day-to-day operations and
- vastly better support for merging between branches. The
- downside is that distribute version control is an inherently
+ are incredible performance for day-to-day operations (because
+ the primary data store is locally held) and vastly better
+ support for merging between branches (because merge algorithms
+ serve as the very core of how DVCSes work at all). The
+ downside is that distributed version control is an inherently
more complicated model, which can present a non-negligible
- challenge to comfortable collaboration. With centralized
- version control, you may find a greater degree of control over
- your versioned assets, especially as regards access control.
- Fortunately, many wise organizations have discovered that this
- needn't be a religious debate, and that Subversion and a DVCS
- tool such as Git can be used together harmoniously within the
- organization, each serving the purposes best suited to the
- tool.</para>
+ challenge to comfortable collaboration. Also, DVCS tools do
+ what they do well in part because of a certain degree of
+ control withheld from the user which centalized systems freely
+ offer—the ability to implement path-based access
+ control, the flexibility to update or backdate individual
+ versioned data items, etc. Fortunately, many wise
+ organizations have discovered that this needn't be a religious
+ debate, and that Subversion and a DVCS tool such as Git can be
+ used together harmoniously within the organization, each
+ serving the purposes best suited to the tool.</para>
<para>Alas, this book is about Subversion, so we'll not attempt
a full comparison of Subversion and other tools. Readers who
More information about the svnbook-dev
mailing list