> In a sane and normal source control > system, Do you mean a "we can't figure out how to implement parallel development so we'll put a straightjacket on our customers and convince them that it's superior" source control system?
> files stay read only until you check them out. Bad Bad Bad Bad Bad Oh how many times I've wanted to smack somebody up side the head for this. This is OK only in some development environments. > CVS seems to be > neither and lets people change files at will. This is quite bad and counter > productive. Have you attempted to understand the theory of operation? I've spent a weekend giving myself a crash course in CVS. Yes, it's different than, say Visual Source Safe, but it's neither wrong, bad, nor counterproductive. I rather like it. Sadly it's freaking another developer out in a big way -- and I have to deal with him. CVS requires a mental adjustment to client-oriented parallel development. The straightjacket is off. I guess it's like freedom. Freedom scares the living daylights out of people conditioned to living under tight controls. -- Practice makes permanent. Perfect practice makes perfect. - Seville _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
