[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Locking support
From: |
Noel L Yap |
Subject: |
RE: Locking support |
Date: |
Thu, 23 Aug 2001 09:50:10 -0400 |
>Greg Woods: Either that or perform some "gentle" re-education on your
>co-workers....
>
>Should we modify the people to suit the software or the software to suit the
>people?
I think a little of both is a good compromise. If you use the "cvs edit -c"
patches, you'll gain advisory locks. Educate the users in how to use advisory
locks properly (eg to effect mandatory locks, tell them not to override the
advisory locks).
Noel
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.
- Re: Locking support, (continued)
- Re: Locking support, Larry Jones, 2001/08/31
- Moving CVS Repository - Uncommited local changes, PRUDHVIDHAR lingala, 2001/08/31
- Re: Moving CVS Repository - Uncommited local changes, Matt Riechers, 2001/08/31
- Re: Moving CVS Repository - Uncommited local changes, Shyam L, 2001/08/31
- Re: Moving CVS Repository - Uncommited local changes, Larry Jones, 2001/08/31
- Re: Moving CVS Repository - Uncommited local changes, Greg A. Woods, 2001/08/31
- Merging changes from main line in to branch, PRUDHVIDHAR lingala, 2001/08/31
RE: Locking support, Noel L Yap, 2001/08/22
RE: Locking support,
Noel L Yap <=
Re: Locking support, Noel L Yap, 2001/08/28