Ketil Z Malde wrote:
> kbrannen@gte.net writes:
>>>[RCS incorporated the]
>>>
>>>>+ branching features of SCCS, and introduced the ability for multiple
>>>>+ developers to work on the same programming project at the same
>>>>+ time.</para>
>>>So I guess SCCS subsequently borrowed this back from RCS, then?
>>
>>Nope. While SCCS used the locking model by default, you could turn
>>that off.
>
> Uh - how is that different from RCS? Doesn't RCS also use locking for
> multiple developers? I thought you needed CVS for concurrent versions
> (and thus the name)?
The difference is in the default. SCCS locks unless you tell it not to, RCS
does not lock unless you tell it to. Other than that, they are conceptually
the same tool. (Yes, I know they have various features that are different,
but I'm talking about the concept of locking while versioning, not who can
annotate/checksum/whatever and who can not.)
(If you'll allow a little CYA...) At least this is how I remember them. It
has been awhile since I've had to use those tools in the raw; but using them
has made me appreciate the "higher level" tools (e.g. CVS, ClearCase, Aegis,
Subversion).
If you have multiple developers doing potentially concurrent work, the 2 basic
models are: lock while you work, or work & merge where necessary. Discussing
which is better my get you into a "religious war"; :-) but I'll tempt fate and
say that my personal opinion is the latter is preferred, but there are times
where locking is useful. No matter which model is used, you can do concurrent
development--I've worked successfully under both models.
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 9 00:16:44 2002