"Markus Karg" <markus.karg@quipsy.de> wrote on 09/01/2005 09:54:03 AM:
> I am using svnserve 1.2.3 and the latest subclipse plugin (thanks to
Eclipse
> auto update).
> Actually I don't want to lock -- it was Subclipse that asked to do so.
> Sure a fresh checkout will also solve the problem, but if you don't have
the .
> properties file in the repository (what is the case here), the Eclipse
project
> settings would be lost. My method of ATTRIB + SVN update solved the
problem
> without loss of that information.
I am not questioning your problem or solution, I am just trying to
understand the ways that we could help solve and prevent this in the UI.
The only time a file should have the read-only attribute set in a
Subversion repository is if the svn:needs-lock property is set. That is
also why I think this is a Subversion bug that they do not clean this up
when the files are added to the working copy.
I think if I add something to the lock dialog that indicates it is coming
up because the read-only attribute it set, that might be enough of a clue
for someone to know that they need to remove those attributes if they do
not want to keep seeing the dialog.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Sep 2 00:05:45 2005