On Dec 21, 2004, at 5:40 AM, Joerg Hessdoerfer wrote:
>
> He doesn't mean locking, he's looking for read-only checkouts (files
> are
> flagged read only by SVN when they are unchanged). This is a feature
> which I
> would also require... will that be in 1.2?
>
We've not ever planned or discussed such a feature...
But, the UI for locking is very close to this. If you attach an
'svn:needs-lock' property to a file in your project, then when you
checkout a working copy, the file in the working copy *will* be
read-only. Only by running 'svn lock foo' will the file 'foo' change
from read-only to read-write. After the lock is released, the file
goes back to the default read-only state again.
This is our way of preventing users from editing unmergeable files
without locking first (and possibly discovering existing locks, thus
preventing time wastes.) The theory is that users/admins would only
set this new property on unmergeable files. But if you want to set it
on everything, that would work too, I guess. You'd have a 100%
read-only working copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 21 15:30:59 2004