[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
cvs commit removed ALL rcs locks
From: |
Stefan |
Subject: |
cvs commit removed ALL rcs locks |
Date: |
Tue, 02 Mar 2004 13:50:01 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 |
We are using cvs admin -l<rev> to set locking on checkout.
When a file, already checked out on the main trunk is
checked out (by a different user) on a branch, a second lock
entry is correctly produced in the repository version of the file.
However, when either user 'cvs commit's the file, BOTH locks
are removed, even if the cvs commit is executed with the -r<rev>
option.
Surely only the lock appropriate to the user (& rev) should be
removed???
a) can anyone confirm this to be a bug?
b) is there any hope of having this corrected in future releases?
c) is there a known work-around?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- cvs commit removed ALL rcs locks,
Stefan <=