On 1/26/07, Thomas M. Hofmann <email@thomashofmann.com> wrote:
> Hi everyone,
>
> I thought this is something that would have come up before but I did not
> find anything about it so I decided to ask.
>
> Is it possible to force and automatic update before locking a file or at
> least issue a warning that the file is not up-to-date.
>
> When someone is explicitly locking a file using the Team-Lock menu item
> for example I don't think this is absolutely necessary but files may get
> locked more implictly by trying to edit the file in some way. The lock
> dialog will come up and if the file is not up-to-date an old revision
> will be locked and edited.
>
> If nothing like this exists I could image an option that checks for an
> outdated file version before the lock is actually taken. A second option
> would be to automatically first do an update and then lock the file.
If the file is not up to date, the lock fails and you get an error in
the console. I am going to follow the Subversion developers on this
one. They debated this issue and decided not to do an automatic
update.
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
Received on Sat Jan 27 01:36:33 2007