[EMAIL PROTECTED] on 02/12/2000 05:43:01 PM >>In my experience the problem is that people want to do their own work as if >>no one else could lock a file. It is generally not locks that anyone >>objects >>to, it is other people's locks. They like to be able to commit changes >>whenever they are ready. > >Exactly. So, how am I going to work when everybody aorund are locking the >files? I have to do the same - bye bye concurency. Again, if someone has "cvs edit -c"'d a file that I want to "cvs edit -c" and I'm told about it, what's the problem? Are you worried about those that'll "cvs edit -f" whenever they feel like it? Maybe those that habitually do this to non-mergeable files should be fired. Noel
- 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
- Re: CVS File Locking Frode Nilsen
