I don't believe the 'edit' does a lock on the server. Quoting Vesperman's book:
"The cvs edit command is used as part of the cvs watch family of commands. If a file is being watched, it is checked out to the sandbox with read permissions but not write permissions. The edit command sets the sandbox file as writeable, notifies any watchers that the file is being edited, and sets the user as a temporary watcher to be notified if certain actions are performed on the file by other users" I did a quick check and a file that I did an 'edit' on did not show up with a lock using 'log'. "Mark D. Baushke" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karr, David <[EMAIL PROTECTED]> writes: > I'm not talking about locking. It's always > impractical to "check out with locks", in any > SCM. Hmmm... 'cvs edit' implies locking, so, your question asked all of us about 'locking' even if you did not know that was what you were asking. > I'm just talking about what happens in the > user's client view. This is not what your message suggested. > I was under the impression before that "cvs > edit" just affects the file in the user's client > view. This is an invalid impression. A 'cvs edit' creates an advisory lock. > Does this also lock the file on the server? Yes it does. -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFA7GOp3x41pRYZE/gRArlBAJ42fM41f3JC3SzF6AZVZAF2vcpOzgCePrRX KnkNL45bavS+GeUT0KlQII8= =quKI -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
