You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Adrian Wilkins <ad...@gmail.com> on 2005/09/02 12:28:49 UTC
Breaking locks on files in renamed working copy folders.
While this is not, per se, a bug, it's something that I feel could
have more automation around it.
* Arthur locks /trunk/projA/foo
* Basil does an svn rename of his working copy projA to projB
* Basil tries an svn commit, and gets the error telling him he can't
delete a file locked by Arthur.
* Basil tries to steal the lock on foo, and gets an error because
/trunk/projB/foo does not exist.
Easily worked around by using a URL instead of targetting the WC, but
this is an annoyance (esp. where it's a bunch of noobs using TSVN).
If it's easy to work out...
- That the WC folder you are in has been renamed, but not committed
AND
- The orginal URL path for this folder
Then it shouldn't be too hard to implement something that can just go
"yeah, I know which file you mean", and steal the lock on
/trunk/projA/foo.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org