svn:needs-lock explanations...

Hi,

I've got a list of binary files in my working copy and each of them has
the svn:needs-lock property set.
If I want to make some changes on a file I have then to get a lock on
it, normal use case here.

My use case is the following now : My working copy of file1.bin has the
svn:needs-lock set. I have a file1.bin elsewhere and I overwrite the one
in my wc with this new one. My OS tells me that I'm going to overwrite a
read-only file as I have acquired the lock on file1.bin. And then I can
commit !

So, I've succeeded in commiting something without acquiring the lock
even if svn:needs-lock was set !

I wonder why the server didn't told me that I could not commit a file
without having previously acquired the lock....

Thanks for your explanations !

Pierre

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-06 15:22:55 CET