The entire idea behind CVS is to *not lock*. The entire idea is that people write their own changes, then collaborate on integration, out of band.
There is no locking, and there never will be. Locking is used as an excuse by people who don't know how to communicate. > Our company has started to look at CVS as an alternative to our current > products. When I suggested using CVS I was told not having a lock file > or method of knowing who was working on some code was going to be > unmanageable. (and nearly beaten to death, by the developers) > > Since Openbsd has the OpenCVS project, I thought you all might be > the best people to ask about this. Is this really going to be an issue > for a handful of developers? > > Thanks in advance for your comments. > > > Roy Morris
