Right-click the file, TortoiseSVN->Properties, and add the following
property:
svn:need-lock
(no need for a value, it will get a value of * automatically, just to signal
that the property is there)
Then commit that change, and ask everyone to update. This will make the file
readonly on everyones machine as they update, and they will be forced to
lock to make it writeable. This basically, for that file, mimicks how other
check in/out version control systems work.
Hope this helped.
On 7/21/07, Helge Nuhn <helge@configo.de> wrote:
>
> Hello mailing list!
>
> I recently deployed Subversion in an office where several people work on
> he same AutoCAD files. Of course, merging two binary files in case of a
> conflict isn't exactly possible. So the regular workflow is locking,
> modifying, committing. As the workers have never used a system like
> this, it happens quit regularly that locking is omitted.
> My question is: Is there a functionality (or perhaps add-on) to
> TortoiseSVN that automatically locks a file when the user tries to open
> it, monitors the thread that currently uses the file, so that closing
> the application results in automatical committing?
>
> I hope my description is clear enough.
> Many thanks in advance for any statement,
> greetings,
>
> ___________________________________
> Helge Nuhn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
--
Lasse Vågsæther Karlsen
mailto:lasse@vkarlsen.no
Received on Sat Jul 21 20:51:05 2007