Re: Ok, how about this -- (locks & lock communication)

Edward Harvey wrote:
> I'll talk to the subversion group, and hopefully get subversion to cache
> (in the entries file) the most recently known remote lock status.

Have fun there! But I think you will get the very same answers as here...

> Based on this information, tortoisesvn can treat a remote lock as an
> implied needs-lock, meaning tortoisesvn can display a gray icon, and
> make the file read-only.

Meaning to abuse the svn:needs-lock property as I already said in another thread
at dev@.

> Users must accept that the information displayed is only as current as
> the most recent update.

You can get the latest recent informations about locks with "Check for
modifications", without needing to update which can cause much trouble. Imagine
someone changed a file in the repository, but you don't want to merge them into
your local modifications right now because you are not finished yet. So you
can't do an update because that would force you to merge your changes.

By using "Check for modifications" you do not alter your local files and
therefore there is no need to do any merging at this time. Of course you should
update and merge your changes with those from the repository before committing.

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Apr 29 13:35:12 2006