On Wed, 2005-02-02 at 22:57, Brian W. Fitzpatrick wrote:
> > Sorry to disturb, but... shouldn't the read-only status of the file
> > tied to the property state *on the repository*? So, a propset adding
> > the property wouldn't do anything, the commit would make the file
> > read-only instead. What's the point of having an uncommited
> > "svn:needs-lock" forcing a local read-only file when everybody else
> > can still freely commit it?
>
> I think that that is part of Greg's (and everyone else's) point, which
> I've come around to agree with now.
I don't think so... I think he's proposing a different way to treat the
property: instead of trying to enforce "unlocked file is set read-only
if svn:needs-lock is set in wc-props", we instead try to enforce
"unlocked file is set read-only if svn:needs-lock is set in base-props".
I can't decide whether that's better or worse. It doesn't seem quite as
consistent as what you initially proposed, but it is simpler.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 3 06:41:02 2005