[EMAIL PROTECTED] on 02/12/2000 04:52:30 PM >Locking help the concurency if moved to it's place. Right now the locks are >everywhere, and at least in my shop, like many others, is wasting CVS and >enforces the locking ALL THE TIME. So, the current implementation does not >help concurency. To completely remove the locks will wipe out the tool from >many areas. THe only way to go is to do it(locking) better.... I don't quite understand your point. Are you saying that "cvs edit -c" and (the forthcoming) "cvs ci -c" isn't enough? If so, why not? Noel
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Tobias Weingartner
- RE: CVS File Locking Paul Sander
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Tobias Weingartner
- RE: CVS File Locking Noel L Yap
- RE: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Kate Ebneter