Quoting "Thompson, Graeme (AELE)" <Graeme.Thompson@smiths-aerospace.com>:
>
> I have just tried this with a subversion 1.2.3 server on SUSE 10 and a
> TortoiseSVN 1.2.6 client.
>
> It does not *Require* you to have a lock in order to commit a file with
> the svn:needs-lock property. You can simply make the file writable and
> then do a commit and it will happily go ahead and update the repository.
>
Yes you're right. However, the commit will fail if someone else has acquired
the lock on the same file. This behaviour works fine in our environment as
we train the developers to use it like this ( and they seem to follow the
standard procedure pretty well ).
> Is there any way to get this to be a requirement, e.g. through a
> pre-commit hook similar to the suggested one to ensure that all files
> have the svn:needs-lock property set?
>
> If so then has anyone got any examples of how to do this?
This would be easy to build using "svnlook propget".
If no one has an example file available I'll create one this evening.
Lieven.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 12 13:20:37 2005