On Sat, 2006-01-14 at 10:13 -0800, Karsten Wade wrote:
I used a proprietary SCM for a while (Perforce) that gives *each*
check-
in a unique, sequential ID. You can not only refer to them by ID, just
like we do with bugzilla reports, but that ID is also a tag of that
check-in. It is representative of the entire repo at the time of the ID
creation, and you can just get the pieces you want.
SVN do that by any chance?
Yup, exactly what it does. The revision number, basically an integer
counting up from 1 (0 if you count the instantiation of the empty repo),
is a reference to the entire repository state. So whereas we use "cvs
<cmd> -r1.3 <file>", where 1.3 is specific to <file>, in Subversion
"cvs
<cmd> -r485 <file1> <file2>" is perfectly sane and refers to two
disparate files' state at a specific point in time. That's why a
command like "svn mv" is trivial in SVN, but has an ugly counterpart in
CVS!
--
Paul W. Frields, RHCE
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project:
http://fedora.redhat.com/projects/docs/