Hello,
This is known bug in CVS when you use "cvs admin -l" to lock the
1.1.1.1 revision. It will actually lock both "1.1.1.1" and "1.1"
revisions. You have to unlock the file using rev tag.
cvs admin -u -r1.1.1.1 myfile.c
cvs admin -u -r1.1 myfile.c
The bug actually happens after you edit and commit the first change
to a file. Commit will create a new revision, which is locked also.
If you are trying achieve "restricted editing" functionality
then "cvs edit -c" is better way of doing this. This will allow
editing only when there are no other "editors" at the same time.
However, you need a patched version of CVS. The latest release of
CVSNT includes this patch already.
Best regards,
Mika Nieminen
--- In [EMAIL PROTECTED], "Dhiradj Ramautarsing"
<[EMAIL PROTECTED]> wrote:
> Release 1.1.1.1 files in CVS. When a release 1.1.1.1 source is
locked, it
> cannot be unlocked. The error message is that multiple revisions
are locked,
> so CVS does not know which version to unlock. This only occurs for
release
> 1.1.1.1. This is probably a known bug. Who knows an acceptable
solution?
