Hi,
The svn:needs-lock property used to prevent commits to files that had
not been locked, but with 1.4.3 it is allowing commits to files that are
not locked and have the svn:needs-lock property.
E.g.
Foo has the property need-lock set.
Foo is not locked
User a changes the file, even though it is read only.
User a commits foo
With 1.4.3 this completes successfully even though the file is not
locked.
Around a year ago using a version around 1.2.3 the commit would have
been rejected...
Is there any way to get the desired behaviour of rejecting the commit
when it is not locked using 1.4.3?
Thanks,
Graeme
************************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 23 11:38:43 2007