-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Correct me if I am wrong, but there is no good reason for the lock_tree_for_write calls in admin.c, edit.c, and watch.c. The three files contain four calls and all are of the form:
~ lock_tree_for_write ~ start_recursion(...CVS_LOCK_NONE...) ~ Lock_Cleanup
with no intervening calls. I believe that in all four locations this could be replaced with the single call to:
~ start_recursion(...CVS_LOCK_WRITE...)
as cvs tag and rtag do and that this would be more efficient, allowing only a directory at a time to be locked rather than locking an entire tree for the duration of the entire operations.
Just wanted to run this by the list before I changed those calls on stable.
Derek - -- ~ *8^)
Email: [EMAIL PROTECTED]
Get CVS support at <http://ximbiot.com>! - -- My name is not Dr. Death. My name is not Dr. Death. My name is not Dr. Death...
~ - Bart Simpson on chalkboard, _The Simpsons_ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQE/hcOuLD1OTBfyMaQRAqnZAKCHoSLFL4lB/ejg18UJKyGEsKZv/QCgvjWd 7bWsJiSUdqZgWLES1cRbdNk= =vA3R -----END PGP SIGNATURE-----
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
