Edward Harvey wrote:
> So I just want to be clear on this --
>
> Basically, everyone is saying (Jody, Sven, Simon, Hans-Emil, Lubbe)
>
> If you don't want someone else to work on a file, presumably because you
> are going to work on it extensively, you must first manually set the
> needs-lock property. You must then manually commit. You must then
> manually obtain lock.
You forgot: you have to force all users to update their working copies or they
won't notice that the svn:needs-lock property is set on this file. And how do
you want to do this?
Subversion is designed to be used offline most of the time, meaning: no access
to the repository. You can't forbid other users to work on a specific file
without setting svn:needs-lock from the beginning, so it is populated to their
workin copies, and not when you want to lock it.
> When you are done, you must manually release lock. You must then
> manually remove the needs-lock property (since it is no longer
> necessary). You must then manually commit.
>
> And nobody is willing to accept any automation of this process.
I don't see any advantage in this process over normal lock without setting
svn:needs-lock.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 29 00:25:16 2006