> -----Original Message-----
> From: Ulrich Eckhardt [mailto:eckhardt_at_satorlaser.com]
>
> I know that some programs actually check if a file is
> read-only when opening it and alert the user that they can't
> edit it. Further, even if you are not using such a program
> you can still claim the lock on the file even if you have
> already opened it and made changes to it. There, I know at
> least one program which still refuses to save to the
> now-writable file, so you will have to write to a different
> file first and then copy it over. All of this is not a
> problem but merely an annoyance unless someone changed it before you.
You're right in that the user can always save the file somehow, but
ultimately this fails in the described scenario, because the user has
not been told that their changes are useless no matter what they do
next, *IF* some other users has remembered to get the lock and changed a
binary file. Unless the tool used to do this has it's own merge
mechanisms that is.
Really the program being used should either clearly warn you about the
read only status of the file, or refuse edits (unless a save as is done
first).
Nick.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-03 14:19:52 CET