[Top][All Lists]

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

Re: Repository know who has checkouts?

From: Noel L Yap
Subject: Re: Repository know who has checkouts?
Date: Wed, 4 Oct 2000 18:30:06 -0400

address@hidden on 2000.10.04 18:11:13
>Noel L Yap wrote:
>> No, unlike some other tools, changes within the repo do not affect
>> already-existing working directories (aka sandboxes).
>I was probably unclear.  If user A sets a watch on somefile.txt, then
>*when user B updates his copy* it will come down as read only, *even if
>there are no settings anywhere in user B's world that would otherwise
>bring a file down read only*.  User B's world has just subtly changed;
>without understanding why, now he just knows that he can't simply open
>that file in a text editor anymore, even though he knows he didn't
>change any environment settings, any file permissions, etc.  If user B
>now gets smart and figures out what's going on and therefore does a cvs
>watch off on somefile.txt, then the next time that user *A* brings down
>somefile.txt it will not come down as read only (as he might have
>thought) but as read/write.
>So user A's sandbox activity can affect the kinds of updates that occur
>later in user B's sandbox, and vice versa.
>Verified using cvs 1.10 on Solaris 2.7 using two users and a pserver
>You can envisage "watch on" and "watch off" wars among the unwashed
>masses.  :-)
>Anyhow, it's kind of a minor point, but it is a little odd, don't you

Yes, this would be a problem.  In practice, though, the entire team decides to
use "cvs watch on" on the entire repository (or at least entire modules) so that
they may use "cvs edit" to better support inter-team communication.


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 & Co. Incorporated, its
subsidiaries and affiliates.

reply via email to

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