[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS - setup reserved checkout

From: Bryon Lape
Subject: Re: CVS - setup reserved checkout
Date: Thu, 11 Oct 2001 17:11:17 -0400

The RCVS part on source forge seems to be dead.  Is anyone really developing
locking for CVS?

address@hidden wrote:

> The most you could hope for in CVS is to install a patch that allows
> advisory locks -- reserved locks are counter to the purpose of CVS.  You
> can find a version of the patch (I think against cvs-1.11.1) at SourceForge
> under project RCVS.
> Once the patch is installed, tell the users that they must have "cvs edit
> -c" and "cvs ci -c" in their ~/.cvsrc files.  Be sure to turn on
> notification as well.  The process they should follow is:
> 1. When intending to modify a file for checkin, "cvs edit" the file.
> 2. If the files are being edited by others, contact the other parties to
> minimize the chances of conflicts.
> 3. If the chances of conflicts is minimal or the others cannot be
> contacted, "cvs edit -f" the files.
> 4. If one receives notification about an as-yet-unknown edit, contact the
> editor to help minimize the chances of conflicts.
> Noel
> Hello all,
> Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
> (Solaris)? Or is there any documentation on this other than the manual
> that comes with the source code?
> If there is any info., please email to address@hidden
> Many thanks in advance
> Andrew
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> This communication is for informational purposes only.  It is not intended as
> an offer or solicitation for the purchase or sale of any financial instrument
> or as an official confirmation of any transaction. All market prices, data
> and other information are not warranted as to completeness or accuracy and
> are subject to change without notice. Any comments or statements made herein
> do not necessarily reflect those of J.P. Morgan Chase & Co., its
> subsidiaries and affiliates.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]