This appendix is a guide for CVS users new to Subversion. It's essentially a list of differences between the two systems as “viewed from 10,000 feet.” For each section, we provide backreferences to relevant chapters when possible.
尽管Subversion的目标是接管当前和未来的CVS用户基础，需要一些新的特性设计来修正一些CVS“不好的”行为习惯，这意味着，作为一个CVS用户，你或许需要打破习惯—忘记一些奇怪的习惯来作为开始。
In CVS, revision numbers are per file. This is because CVS stores its data in RCS files; each file has a corresponding RCS file in the repository, and the repository is roughly laid out according to the structure of your project tree.
在Subversion，版本库看起来像是一个单独的文件系统，每次提交导致一个新的文件系统；本质上，版本库是一堆树，每棵树都有一个单独的修订版本号。当有人谈论“修订版本54”时，他们是在讨论一个特定的树(并且间接来说，文件系统在提交54次之后的样子)。
Technically, it's not valid to talk about “revision 5
of foo.c.” Instead, one would say
“foo.c as it appears in revision
5.” Also, be careful when making assumptions about the
evolution of a file. In CVS, revisions 5 and 6 of
foo.c are always different. In Subversion,
it's most likely that foo.c did
not change between revisions 5 and
6.
Similarly, in CVS, a tag or branch is an annotation on the
file or on the version information for that individual file,
whereas in Subversion, a tag or branch is a copy of an entire
tree (by convention, into the /branches
or /tags directories that appear at the top
level of the repository, beside /trunk). In
the repository as a whole, many versions of each file may be
visible: the latest version on each branch, every tagged
version, and of course the latest version on the trunk
itself. So, to refine the terms even further, one would often
say “foo.c as it appears in
/branches/REL1 in revision
5.”
更多细节见“修订版本”一节.