RE: Pre-commit Hook

>If you want to prevent users editing the file without getting the lock,

>then set the svn:needs-lock property. As well as enforcing what your
>trying to do with a script, it also makes these files read-only in
their
>working copy until they obtain the lock.

Thanks all,

I tried both procedures and finally got them working, the pre-commit
hook was pretty hard I have to say and it works great with existing
files, it requires the user to lock the files before commiting any
changes... BUT
I just tried to add new files and it wouldn't let me because my "new"
files are not locked =|... Well they are not under revision control so I
can not lock them. I also tried creating folders and deleting files with
the same results...

Is there a way to distinguish a 'delete file/folder', 'add', 'import' or
'mkdir' transaction from a 'file changed' transaction?

Thanks in advance for your help,

Ignacio
 

---------------------------------------------------------------------
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-01 01:11:09 CET