RE: rcvs patches

[Noel Yap]

It's a bad idea to have several developers within the
same sandbox since it's very easy to have them trounce
each others' changes, break the build, overwrite a
build that's being used, ...  In fact, if you start
changing permissions in order to help avoid these
problems, CVS won't work properly since noone will be
able to perform an update if they can't overwrite all
the files within the sandbox.  So, don't share
sandboxes.

If you want advisory locks, rather than reserved
locks, the last time I checked, it's the latest patch
on the list.  I'm not sure if it needs to be applied
to cvs-1.11, cvs-1.11.1, or the latest development.

If you need help applying a patch, man patch.

Noel
--- "MW Mike Weiner (5028)" <address@hidden> wrote:
> yes this is what we had in mind...we are trying to
> mimic the locking
> mechanism that was inherent in MS Visual Source
> Safe, so we can have
> multiple developers editing the same file in
> separate (or even the same)
> sandboxes. The next step is which patches do i need
> from the rcvs project to
> use with the current cvs-1.11 install??
> 
> Thanks.
> Michael Weiner
> 
> -----Original Message-----
> From: Noel Yap [mailto:address@hidden
> Sent: Friday, January 18, 2002 9:01 PM
> To: MW Mike Weiner (5028); 'address@hidden'
> Subject: RE: rcvs patches
> 
> 
> The locks that "cvs edit -c" affords are advisory
> which means that they are only locks in-so-far as
> users treat them as locks...  Users can always use
> "cvs edit" or "cvs edit -f" to go ahead or force the
> edit.  If this is what you had in mind, then the
> patches are perfect.  If not, why not?
> 
> Noel


__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/