Yes, which is basically a pass through to RCS level commands.
My understanding is that CVS ("Concurrent Versions" System) wasn't designed
in the model of "checkout the source and lock it" ( like SCCS does).
CVS has a model of using the "edit" command which indicates to other developers that you have the intention of making changes to the file, through the cvs "watch" email notifications and r/w permissions on the file vs r/o permissions. If you decide you do not want to make the changes you perform cvs unedit on the files (sort of like unget). But edit and unedit are more "honor" system notifications than strict locks. My company never used them, and only rarely used the cvs watch on a few key files.
Ultimately it is the original version ID that was checked out into the sandbox, which CVS will use to determine if it can commit the file, or force the user to run an "update" first. In that sense, maybe you don't need to lock the file. If changes have gone into the repository in the meantime, you will be forced to merge them in through the update command, before you are allowed to commit.
Hamid Ghassemi <address@hidden> wrote:
You will have to use the admin menu and choose command line and then add cvs admin -l command for locking any file.
I am using Windows server as CVS Server machine. I have installed CVSNT Server and WinCvs Client.
Its is working fine, but after checkout of files, they are not locked for a single user. How do i lock the files
From anybody else editing it.
Info-cvs mailing list