If you can, try using the "reserved edit" patches available at SourceForge under
project RCVS. These patches "replace" reserved locks by increasing
communication among developers.
In your specific situation, for example, if another user unedits someone else's
edit, an email will get sent out regarding the action (assuming you've
configured the email feature properly). So, barring any developer hacking, all
watchers will at least know what's happened to the file.
IMO, there is absolutely no need for absolute reserved locks within a team of
cooperating and communicating developers.
Noel
[EMAIL PROTECTED] on 2000.12.19 07:30:47
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: locking a file
I have aproblem that a user can unlock (cvs admin -u) a file locked
by other developer. Is there a way to prevent this behavior?
p.s
I'm using cvs 1.11 on Linux
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
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.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
