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

Re: [REQ] Unset read-only attribute

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-08-29 22:42:20 CEST

On Mon, 29 Aug 2005, Mark Phippard wrote:

> Scenario:
> User is migrating from another version control tool like ClearCase or PVCS
> that makes files read-only on checkout. They copy these files into a
> working copy and do an add and commit. Currently, Subversion does not
> unset the read-only attribute even though the svn:needs-lock property is
> not set on the files.
> Problem:
> Subclipse and TortoiseSVN both use the read-only attribute as a hint that
> the needs-lock property is set and use this to set a decorator indicating
> that a lock is needed before editing. We do this because it is a lot
> faster and I believe at one time Subversion had problems if it ran into a
> file with the read-only attribute set.

In my wc-propcaching work (see the branch with the same name), I intend to
make the svn:needs-lock property available in the entries file for this
very reason, GUIs often want that information and reading each property
file just to get it hurts performance.

(Yes, there hasn't happened much on the branch yet, but that's because I'm
currently occupied by other things right now.)

Maybe this can improve the situation.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 29 22:43:04 2005

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

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