On Tue, 2005-04-12 at 17:39 -0600, D.J. Heap wrote:
[snip]
> The second issue is probably Windows only -- assuming the needs-lock
> property was on the file and you run the above transcript, if you issue
> an 'update' and get a conflict, the file.txt is read-only and cannot be
> edited. And on Windows it cannot be reverted either -- the revert fails
> with 'Access denied' due to the read-only flag. It seems like a
> conflict should leave the file editable, and revert (and possibly other
> commands?) need to pay attention to the needs-lock property and remove
> read-only-ness when necessary.
Kind of related to the above...if you have a needs-lock file that is
*not* locked and make changes to it (overriding read-only-ness), doing a
revert will not put back the read-only-ness on Windows or Linux. It
seems like it should...
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 13 01:52:14 2005