Re: Enforcing the lock of a file prior to its commit.

Luca Cappa wrote:
> No, cause if you try it, you could commit a file with that property set
> even though you havent locked it. The trick is to just remove the
> read-only flag on that file, modify it and then commit it. Try it and you
> will see
> that locks as they are appear to be totaly useless.
>

You need better discipline in your team. If a member of my team changed
the read-only flag to edit the file without locking it, they would get a
very quick and stern reprimand.

-- 
Sly
This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org