Re: Forcing locks on files when checked out..

2001-12-05 Thread Noel Yap
I think the easiest way to do this (although I may be biased) is to install one or some of the patches available at SourceForge under project RCVS. The patches I'm thinking of will add checking to edit and commit. Developers will need to modify their .cvsrc files to default to the right command

RE: Forcing locks on files when checked out..

2001-12-05 Thread Ronald Landheer
. ;) Thx so far! Ronald > -Original Message- > From: Noel Yap [mailto:[EMAIL PROTECTED]] > Sent: woensdag 5 december 2001 14:41 > To: Ronald Landheer; [EMAIL PROTECTED] > Subject: Re: Forcing locks on files when checked out.. > > > I think the easiest way to do th

RE: Forcing locks on files when checked out..

2001-12-05 Thread Noel Yap
ours truly if > they're gonna be done at > all.. (I need a rather authorative/authoritarian > setup for just about > everything here). > > In a week or so, they'll be happy having a CVS.. ;) > > Thx so far! > > Ronald > > > -Original Message-----

Re: Forcing locks on files when checked out..

2001-12-05 Thread Martin Ellison
> I'm hoping to find a server-side only config, because the induhvidual > settings would have to be done by yours truly if they're gonna be done at > all.. (I need a rather authorative/authoritarian setup for just about > everything here). The problem is that the client and the server need to col

Re: Forcing locks on files when checked out..

2001-12-06 Thread Noel Yap
He could patch the client so that it passes the "right" options (eg "cvs edit -c" and "cvs ci -c") in by default. Noel --- Martin Ellison <[EMAIL PROTECTED]> wrote: > > I'm hoping to find a server-side only config, > because the induhvidual > > settings would have to be done by yours truly if > t