[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: workaround request

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2006-12-04 19:11:24 CET

Stefan Küng wrote:
> Gerasimov, Ivan wrote:
>> 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.

And even if such a thing were implemented for added files, it still
wouldn't help when you want to delete a directory that contains such
'hidden locks'.

It seems the real fix is a little more complicated than expected,
so the best approach for svn admins right now, IMO, is to write a
post-commit hook like:
        for every deleted file
                if deleted file is locked then foribly unlock

This is a much better way for the end users than adding any semi-hack UI
that requires manual steps on their part.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 4 19:08:47 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.