> 2.) It won't solve your problem. Even if you set the
> "svn:needs-lock"-property and commits, this won't be known by the others
> until they have done an update. This means that when setting the property on
> a file you will be in a "unstable" state until everyone has done an update
> and received this change. Until then the property is as useful as the lock
> by itself. Point being: Everyone needs to have the property on the file in
> their WC *before* you get the lock. There is no other way to guarantee this
> than setting the property when the file is added.
This is what I was trying to stress to Edward in my first response.
Since other users won't get the read-only unless they commit it all
makes no sense to me. It'd be easier for them to just do a check for
modifications instead of an update when they go to edit a file they
think might be locked by someone else.
So once again, what is wrong with your users who are so afraid of
merges just making more use of the "Check Repository" in the "Check
for Modifications" dialog?
- Jody
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Apr 28 17:56:44 2006