[REQ] Unset read-only attribute

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.

Request:

When you run svn add on a file that has the read-only attribute set, the
attribute should be unset.

Thoughts? Can I file an issue?

Thanks

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
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:35:41 2005