[cvsnt] Why edit -x?

[Torsten Martinsen]

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