AW: AW: Cleanup failed, please execute the 'Cleanup' command.

Hello Stefan!

> Cleanup removes write locks. Those are not the same locks as those set with svn:needs-lock!
> write locks are used to prevent multiple svn clients from writing at the same time to the working copy database. Like mutexes/semaphores in multi-threaded apps.

> So you don't have to worry about your svn:needs-lock locks. And if your working copy is not
> shared with other users and you don't have another svn client running e.g. an update or
> some other command on that same working copy, you *should* check the box "remove locks" when doing a cleanup.

If the "break locks" check box in svn cleanup targets database locks, not "svn:needs-lock" type locks,
could the text be changed to "remove" (as you wrote - probably not intentionally) or "clear database locks"?
In my opinion "breaking locks" is (should be) reserved for the high-level
subversion operation of me needing to change a file that my buddy reserved for himself.
If we can choose a different wording for different locks, IMHO the situation would improve.

Hartmut

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3162288

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-02-22 14:32:51 CET