[cvsnt] Problem with Checkout Read Only

Edwin Gijsbregts edwin.gijsbregts at ubench.com
Fri Jan 17 16:57:34 GMT 2003


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Hi,

I'm new to CVS and noticed a problem that is (I think) similar or the same
as the problem Erik mentioned.
On my fresh installation of CVSNT (cvsnt-1.11.1.3-65) and WinCVS
(cvsnt-1.11.1.3-57k) I check-out a module with option read-only.
All files appear in my local workspace, BUT read/write, while I expected
them to be read-only (is that the right assumption ?).
The fact that it isn't read-only on checkout will be fixed in build 66 then
?

Then, after I edit one of the files and commit it, the file has a new
revision number AND then it becomes read-only !
When I then want to edit the file I choose "reserved edit". Another
developer tries to access the same file, with "reserved edit" but the file
appears locked to him. But when he chooses "Edit" (thus not reserved") he
can still access and edit the file. Is this normal ? What is the use of the
locking then.

I know that CVS encourages a team not to apply locking, but we are currently
looking for the best way to use CVS within our team.

Best regards and thanks in advance for all help,
Edwin







More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook