[cvsnt] Why edit -x?

Torsten Martinsen torsten at tiscali.dk
Sat Oct 2 21:17:04 BST 2004


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.


Jerzy Kaczorowski wrote:

>E.g. someone will do edit -x, forget about it and go on for holidays. Others
>are stuck. 
>
As Tony said, an admin can fix that case.

>Or someone will lock the whole folder with all the files, even if
>working on a couple of files 
>
That is not a technical problem, that is a people problem. Anybody doing 
that should only get one warning before getting kicked out.

>and it takes time to track that down and beg
>the guy to un-edit it. Or the "manager" is not comfortable with concurent
>development model and will force everyone to use that. 
>
Annoying, but a PHB might as well force his team to use PVCS, 
SourceSafe, etc.

I agree with Tony that concurrent edits are to be preferred, but having 
"exclusive" functionality in CVSNT actually makes it easier to convince 
management to switch from a non-concurrent SCM to CVS. And after that, 
it's easier to sneak in concurrent development :-)

-Torsten



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