Stuart R Dole writes:
>
> I've discovered that when I cd into a working directory,
> after logging-in to cvs, that cvs doesn't like me to do
> things unless the name in CVS/Root is me. This makes sense,
> but since there's several of us that telnet into the
> "workstation" and modify files, each one needs to edit the
> file CVS/Root to match themselves. (I haven't figured out a
> good way to simply let each user have his/her own working
> directory -- there's one working directory on the
> workstation that we all share, because of the way all the
> scripts are set up... The workstation is really an embedded
> system with custom hardware on it that we're constantly
> testing.)
Yuck! How do you prevent two people from telnetting in to the same
workstation and stepping on each other's changes? CVS was never
intended to handle that kind of an environment. About the only thing I
can suggest is always doing ``cvs -d $CVSROOT'' to override CVS/Root.
-Larry Jones
They say winning isn't everything, and I've decided
to take their word for it. -- Calvin
