[Top][All Lists]

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

Re: Reserved checkouts.

From: Noel L Yap
Subject: Re: Reserved checkouts.
Date: Wed, 2 May 2001 10:49:34 -0400

address@hidden on 2001.05.02 10:21:54
>What you want is some way of controlling who's working on the
>file at any given time, and the CVS way to do that is to set
>"cvs watch on" all files that you want to control, and ask
>the developers to use "cvs edit" to unlock them.  This isn't
>strict locking, but rather advisory.  Having worked with both,
>I can testify that strict locking doesn't stop people from
>working simultaneously on a file and blowing away other people's
>changes, and advisory locking seems to work as well as strict.

I think that advisory locking works better than strict locking since developers
are still working within the version control tool rather than circumventing it.

>(Noel Yap wrote some patches to put teeth into the watch/edit
>process, and these can be found at the RCVS project at Sourceforge,
>last I looked.  These patches were written against an earlier
>version of CVS, so use with caution.)

I've updated the patches against cvs-1.11, but they're not as well tested as the
ones on SourceForge (since I haven't been using CVS as of late).  These new
patches haven't been posted on SourceForge (yet) so I'll send them out to those
who ask.  Anyway, "use with caution" still applies.


I'm still looking for volunteers to patch the docs and tests so that these
patches have a greater chance of making it into the "official" CVS release.

David H. Thornley                          Software Engineer
at CES International, Inc.:  address@hidden or (763)-694-2556
at home: (612)-623-0552 or address@hidden or

Info-cvs mailing list

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]