Re: [Subclipse-users] Warn on unlock with uncommitted changes

On 1/26/07, Thomas M. Hofmann <email@thomashofmann.com> wrote:
> Hi again,
>
>
> this has come up on the subversion list but was not discussed any
> further. This has also come up as a requirement in our team.
>
> When a file needs locking and the user has locked the file and made any
> changes and then unlocks it again subclipse could optionally issue a
> warning that someone else may take the lock and thus make conflicting
> changes.
>
> I personally think that if someone is actually doing the unlock the
> consequences should be clear but some users have a different opinion on
> that.
>
> What do you think?

I cannot imagine adding something like this. I do not see it as being
much different than warning someone before commit that they should
make sure they made the right changes. At some point the tool needs
to get out of the way and the user needs to assume responsibility for
what they do with it. User's can get confused by anything. They make
mistakes and eventually they learn. That is basically how we all
learn,

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org