On 4/27/06, Edward Harvey <eharvey@chilsemi.com> wrote:
>
> What do you think about this idea --
>
> When a user locks a file, tortoisesvn simultaneously sets the "needs-lock"
> on that file. When the user unlocks, it automatically takes off
> "needs-lock."
>
> This behavior could be made optional with a checkbox in the tortoisesvn
> settings. Personally, I would use it and habitually set that checkbox for
> all my users.
>
>
The problem is that changing a property requires a commit, so using
such a method would mean 1 extra commit to set the needs lock, and all
the handling to go around that. Then if you release a lock without
commiting, it has to unset the needs-lock with another commit again.
This seems really messy, and it'd only be a benefit if other people
updated their working copies to get the new needs-lock property
change.
I really don't see any benefit to this. Rather than people having to
do updates all the time why not just have them do status checks all
the time? Is it really that harder to just leave a "Check for
Modifications" dialog up all the time and have users periodically
click "Check Repository"? They'd always have a window showing what
the last known locked files or updated files were and they could
always update it just before modifying a new file. All of your
proposed changes seem to me to be way too complicated for very little
gain and would be much better solved by users just using the existing
tools and communicating better.
- Jody
- Jody
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 27 20:10:58 2006