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

Re: [TSVN] Locked overlay

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-04-13 20:34:58 CEST

SteveKing wrote:
> Molle Bestefich wrote:
>> SteveKing wrote:
>>> - file is readonly
>>> But we don't really need an overlay for that - the explorer already has
>>> a built-in column provider to show the file attributes.
>> Doesn't count.
> It counts.

It doesn't, for the reason cited below.

>> - Nobody has that lame column turned on, because it's basically useless.
> Well, it will be once you have locking in place.

Reason cited below.

>> - Forcing users to turn it on when we're communicating everything else
>> with overlays is wrong.

Well, let's get a little meat on the discussion...

>> - Just because a file is set read-only by svn when it's
>> svn:needs-lock, doesn't mean that a read-only file by implication also
>> has svn:needs-lock. Those are different things.
> I know. But you don't have readonly files inside a working copy unless
> the svn:needs-lock property is set (Subversion would error out if a file
> is readonly on every update).

Taking over an attribute that's used for a ton of things and then
relying on it to never change beyond what you do to it - that's just
broken by design.

I surely hope you're not serious that SVN will die if a file is read-only.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Apr 13 20:35:31 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.