Check Locks (CHECKLOCK)
The CHECKLOCK attribute tells QVCS whether or not to bother with QVCS archive lock requests. If CHECKLOCK is on (the default), then before a revision may be put into a QVCS archive, the individual adding the revision must hold a lock on the revision. Typically the user would perform a Check-out operation before making any revisions, both fetching the most recent revision from the QVCS archive and locking the revision. However, just a Lock operation would be sufficient.
Having locks is a way to let others know that you are working on a particular file revision. If someone tries to get a lock on a revision that has already been locked, QVCS denies the request, shows them that the revision is already locked, and shows them who holds the lock. This prevents people from making concurrent changes to the same revision. Only a person holding a lock is allowed to update that revision. If anyone tries to add a revision to a QVCS archive that they don't have a lock on, their request is denied. This feature has obvious utility in networked situations, and in situations where more than one person works on a project file.
When CHECKLOCK is disabled, then QVCS ignores any lock requests, and you don't have to hold a lock on the QVCS archive in order to add a revision to the archive. Adding a revision is always allowed, provided the user adding the revision is on the archive's access list. You may find this convenient for one-person projects, where it may not be worth the bother of locking QVCS archive revisions when no one else is going to access them. However, locks can serve as a reminder of which revisions you are changing.
Note that in order to use automatic branching, lock-checking must be enabled.
QVCS Attributes
|
