Re: Atomicity of locks and needs-lock

Edward Harvey wrote:
> [snip long story]

You have a good point.
It's not obvious to users that they cannot lock files if it does not
have "needs-lock" set.
There's still a "lock" command, and in a GUI it's ever-so-present,
even on non-needs-lock files.

But applying needs-lock automatically is not the solution.

The solution is to warn users "needs-lock is not set on this file,
what you're doing is useless. Go read the manual..." if they try to
lock it.

And removing the lock menu item from the GUI on all files that do not
have needs-lock is another good preventive measure, although it cannot
be applied entirely (users might select multiple files, etc etc.).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 29 12:47:45 2006