[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: |
Tue, 28 Aug 2001 16:06:30 -0400 |
>PooPoo. I've used CVS for years and have avoided that "insecure"
>feeling some of us get from not knowing if we are working on a file
>that someone else is working on. We've wrapped cvs edit in a perl
>script that determines who else is editing the file and warns (ok
>informs, if that makes you feel better) you who is editing the file.
Why wrap CVS when you can install the patches (available at SourceForge under
project RCVS)?
I suppose if you already have something that works, why bother? However, keep
in mind that there may be a race condition in your wrapper script.
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, Eric Siegerman, 2001/08/31
- 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, 2001/08/23
Re: Locking support,
Noel L Yap <=