Re: Restrict while commit? File must be locked!

[Todd Denniston]

> Dear List,
> 
>    What happened when developers are not ready to accept good solution! 
> 
> Any way we want to move from PVCS to CVS but the developers are addicted by 
> the  
> Lock-Modify-Unlock model and they wanted the file must be locked
> 
> before commit. They are appreciating the features of CVS Otherwise !!.
> 
> Can I check before commit that the file is locked or not?
> Any suggestion or link is highly appreciable.

the thread in the archive[2] "Really a reserved checkout?", from Feb 2003,
could be useful to you.

from the cederqvist[1] have them read the section '10. Multiple developers'
and specifically '10.7
Choosing between reserved or unreserved checkouts'.

Then look at implementing reserved checkouts in section '10.6 Mechanisms to
track who is editing files'.

To get stricter locking  "take a look at the advisory locks patch available at
SourceForge under project RCVS." _Noel Yap_2002.
I am not sure, but I think the advisory locks patch may have been incorporated
into 1.12.x and/or cvsnt[3].


the thread in the archive "Really a reserved checkout?", from Feb 2003, could
be useful to you.

[1] https://www.cvshome.org/docs/manual/

[2] http://lists.gnu.org/pipermail/info-cvs

[3]  http://www.cvsnt.com/

{I would have dropped you direct links, but I am queuing this up to go out
when they figure out where the backhoe found the internet line. :}
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter