[Top][All Lists]

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

Re: Strict Locking for checkouts

From: Noel L Yap
Subject: Re: Strict Locking for checkouts
Date: Wed, 14 Feb 2001 14:19:56 -0500

address@hidden on 2001.02.14 10:32:28
>    I need strict locking because all the developers are checking out the files
>into the same shared filesystem structure. If I dont use locking the users will
>overwrite other users checkouts. I'm thinking about to write a patch to provide
>with pre-checkout features for this pourpose (like the existing pre-checkin
>provided by commitinfo) Also i'm thinking about to patch CVS to force strict
>locking with each checkout. Please let me know if you have any usefull tip or a
>better approach to this sollution. Thanks in advance.

It's much, much better if developers check out into their own working areas,
then copy (aka install) their modified files into the shared area.  You'll still
wind up with the problem of people writing over each others' files, but at least
they'll still have their own copies so nothing is lost.

Over here, I've been trying to get people to set their umask to create files as
group read-only to help prevent accidental overwrites within the shared areas.
To prevent serialized development, the directories are made group read-write so
that developers can move or remove others' files.

In the future, we'll have separate, complete environments so all this will be


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

reply via email to

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