SteveKing wrote:
> Just played a little bit with lock/unlock:
> - an already locked file can't be locked again even if the username
> matches (i.e. if the user himself has the lock already - relocking is
> not possible). That lock would have to be stolen too.
Yes, this is to prevent cases where (for example) you lock a file on
your desktop PC and try to edit it later in a different WC on your
laptop. Your desktop might have local changes that you don't want to
lose, even though you own both WCs. That's why I didn't say "locked by
another user" in my suggestion but "locked in another working copy".
> - If multiple files should be locked, the whole operation stops on the
> first failed lock, so no list of files which aren't locked. Either all
> or nothing.
I thought TSVN always treated operations on multiple items as many
single operations instead of one big operation? Although I guess this
would be undesirable during locking, since they are immediate changes
which require a commit message.
Another way to accomplish this would be to have TSVN check itself
beforehand whether any locks already exist, before it actually attempts
locking them. This way you could still show the list of already-existing
locks and offer the "steal" option, and the only time this would fail is
the race condition where someone grabs a lock between when TSVN polls
the repository and when it attempts to grab them, but this would be much
rarer I'd think.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Apr 8 22:54:23 2005