Hello,
-----Mensaje original-----
De: Nick.Thompson_at_infineon.com [mailto:Nick.Thompson_at_infineon.com]
Enviado el: lunes, 03 de marzo de 2008 13:20
Para: users_at_subversion.tigris.org
Asunto: RE: Re: Get exclusive lock
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).
-----------------------
I wanted to thank all those who have responded to me. I have the "solution",
thanks to a colleague who uses VSS and he has open mind ... (not closed only
to VSS) :-) In VSS, if you does checkout (same that svn with get lock), I
thought that if someone else opened the same document, it is opened and
could not write in it (the colleagues that use VSS said me it), and it is
false, it depends on the program that you use for opening the file. For
example, my colleagues use Ultraedit, for editing files, and Ultraedit
doesn't allow write in the file (because it detects that the file is opened
in read-only mode), but Word, even if the file is in read-only, allows write
in his files (.doc's), don't save, but you can waste time writing in it, so
VSS and SVN, with svn:needs-lock property, behavior is the same (thanks to
Ulrich Eckhardt for his comment too).
I wait that you can understand my bad English :-) Finally, my colleagues
will have to use svn x) I hope that they don't say another excuse ......
Thanks to all.
Cheers...
---------------------------------------------------------------------
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 16:42:53 CET