CVS itself grew from an older versioning system, Revision Control System (RCS).
RCS handled individual files, but not whole projects. Although statistically CVS is
still widely used, the popularity of Subversion is steadily growing and it has been
said that people switch to Subversion just because they want to use Trac! Many
high-profile open-source projects including Mono and Ruby on Rails use Subversion
for their version control requirements, and Sourceforge (http://sourceforge.
net/) provides Subversion in addition to its traditional CVS hosting while Google
Code (http://code.google.com/hosting/) uses Subversion exclusively.
Some of the concepts discussed here may be new to those unfamiliar with revision
control, but they will be explained in Chapter 7.
Subversion's features include:
Feature compatibility with CVS: As it is intended to be an improved CVS,
most of the features are implemented so as to behave similarly to their
CVS equivalents.
???
Chapter 2
[ 17 ]
Versioning for folders, renames and properties: All these features are
missing in CVS, which is one of the most common complaints against it.
In addition to files and their contents, Subversion provides versioning
for folders and support for renaming. It also allows arbitrary metadata
("properties") to be versioned along with any file or directory, which amongst
other things provides a mechanism for retaining 'execute' permission flags
on files.
Pages:
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38