Ben Collins-Sussman wrote:
> By the way, before playing with locks, you might want to read:
>
> http://svn.collab.net/repos/svn/trunk/notes/locking/locking-ui.txt
>
> ...so you know what to expect.
>
Just looked at this and I have some questions. We are using a tool
(Maya - http://www.alias.com/eng/products-services/maya/) that
unfortunately falls under the "Hijacking Scenario" and silently ignores
the read-only attributes of files until it's too late. Many of my users
are type 2 users (although I'm gradually converting them). What is the
recommended way of preventing hijacking? With a hijacking editor is
there any advantage of using svn locking? Is there a way (or a way
planned) to require a user to hold a lock token in their wc in order to
read a file?
-Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 22 18:17:57 2005