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

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

From: Edward Harvey <eharvey_at_chilsemi.com>
Date: 2006-04-29 18:46:29 CEST

> > 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...

What answers are you talking about? Same answers don't apply to
different questions.

> > 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@.

Not at all.

I am saying, DON'T set the needs-lock property if you don't feel a file
always needs-lock. But as long as a lock exists on a file, it implies
that right now it needs-lock. So as long as the lock exists,
tortoisesvn can gray the icon and make the file read-only.

There is no abuse of any property in this situation.

> > 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

That's right, you can find out the information, but you personally have
to remember in your brain, while computer memory is much better than
your memory. Why not let the information be cached on disk instead of
in your brain.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Apr 29 18:46:54 2006

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