[Top][All Lists]

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

Re: Repository know who has checkouts?

From: Richard Wesley
Subject: Re: Repository know who has checkouts?
Date: Wed, 4 Oct 2000 15:39:07 -0700

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

I would think that folks who are using the watchers/editors mechanism would always be getting files read-only, simply to help remind them to use cvs edit.

I am also sort of surprised that your text editors will not open read only files. All of mine do - they just won't let you modify them. My IDE will even ask you if you want to do file checkout (i.e. cvs edit in cvs) if you try to change them.

- rmgw

Richard Wesley           Electric Fish, Inc.       address@hidden

"Grownups have the most uninteresting explanations for things."
                 - C. S. Lewis, _The Magician's Nephew_

reply via email to

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