Hi Andreas, Please see my comments below.
On Mon, Jul 28, 2014 at 03:04 PM PDT, Andreas Stieger wrote: AS> Hi, AS> On 28 Jul 2014, at 22:38, Mun Johl <mun.j...@emulex.com> wrote: AS> AS> I have an XML file checked in with the svn:needs-lock property set. I AS> verified that the permissions on the file in the filesystem do not AS> include write permission. AS> As a test, I made a small change to the file and attempted a check-in AS> (w/o first locking the file). To my surprise, the file update was AS> applied! AS> Is this a known bug with the version of SVN I'm using? AS> Are my expectations incorrect? AS> AS> See http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html#svn.advanced.locking.lock-communication AS> The property indicates to clients that the item should, not must, be locked. It is, along with AS> locks, a communication tool to synchronise edits to files which are not textually merge-able. AS> Most clients support this and prompt the use to acquire a lock. AS> AS> That is, am I doing something AS> incorrectly if I want a user to have to lock the file prior to check-in? AS> AS> You mean prior to editing? AS> You may attempt to enforce locking via hooks but that would undermine the concepts of AS> breakable / steal-able locks in svn. I am in fact planning on using a pre-commit hook for our needs. Thanks, -- Mun
