Gerasimov, Ivan wrote:
> Hello, Tobias!
>
>> The following workaround originally posted by Stefan should work:
>>
>> ----------------------------------------------
>> Unfortunately, you need the svn client to recover from this:
>> svn unlock --force url/to/nonexisting/file
>> ----------------------------------------------
>>
>> see http://svn.haxx.se/tsvnusers/archive-2006-08/0074.shtml
>>
>> I'd prefer not implementing a workaround in TortoiseSVN since the
> problem
>> can be solved with the command line client and is not that common.
>
> Ok, I can see that.
> Though, this problem is still quite common for some of my users, who
> mostly work on binary files.
>
> Then what about some simple GUI, which allows breaking that kind of
> locks?
> The simplest one would be a 'unlock' menu item in the context menu in
> the 'check for modifications' dialog.
> If you added a new file in place of that deleted-locked one, the dialog
> shows you the lock information for the added file.
But how would TSVN know that your newly added file was deleted before?
It can't know that without receiving the log first (which is not
acceptable for those dialogs).
Without knowing that, we would have to show the context menu command for
all added or unversioned files, which would be plain wrong.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 4 18:58:17 2006