On Apr 15, 2005, at 11:53 AM, Lan Barnes wrote:
Again, I would strongly recommend that you put CVS out of your mind for
life. Use subversion for real projects
If you are working on a "real" project, I agree that you need to make an active decision about your source code control system and it probably should not be CVS.
Subversion, darcs, and arch should be on your list from the open source side. Perforce seems to be pretty good on the closed side. The *BSD developers have been using Perforce for various efforts which diverge from the standard codebase for quite a while; they seem pretty happy about it. This is especially ironic given how noisy the Linux/BitKeeper flap has been.
, RCS for simple applications. CVS belongs in the ash heap with SCCS.
RCS fails on the front of not allowing you to check out a copy of the code when some other idiot accidentally grabbed a lock and forgot to release it.
CVS can have merge issues, but I get *far* fewer merge issues with CVS than lock issues with RCS (shivers with flashbacks).
-a
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
