[EMAIL PROTECTED] on 05/30/2000 10:30:49 PM
>Can you just ask all developers (under penalty of corporeal punishment for
>noncompliance) to execute a "cvs editors" on each file they intend to
>modify? If anyone is currently editing the file, the developer should not
>"cvs edit" nor modify the file.
There's a small chance that more than one person will do "cvs editors" at the
same time and see that noone is currently editing the file. They then do "cvs
edit" on the file and they all get punished unless the punisher actually looks
at the edit timestamps and sees they're off by just a few seconds.
The entire purpose of creating the "cvs edit -c" patch was to absolutely prevent
such situations -- either all the edits go through, or none of them (assuming no
catastrophic events occur, of course).
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 & Co. Incorporated, its
subsidiaries and affiliates.
