[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Edward Harvey <eharvey_at_chilsemi.com>
Date: 2006-04-29 01:52:27 CEST

Ok, I've heard the least objection to this idea, so let me run it by one
more time --

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

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.

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

> -----Original Message-----
> From: Edward Harvey [mailto:eharvey@chilsemi.com]
> Sent: Friday, April 28, 2006 6:10 PM
> To: users@tortoisesvn.tigris.org
> Subject: Ok, how about this -- (locks & lock communication)
>
> At present, if a file has the needs-lock property,
> tortoisesvn will make the file read-only and mark it with a gray icon.
>
> Would it be ok to do the same thing, if the file is locked by
> some other user?
>
> Tortoisesvn will not remove the gray icon, or make the file
> writable, until you do an update, and either the needs-lock
> property, or the remote lock have been removed.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Apr 29 01:52:48 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.