Ryan/Erik,
Thank you! This gives me plenty to get started with.
_Marvin
---------------------------------------------------------
| USA Cell: 248.866.4897 (free incoming)
| Message: 2488664897@messaging.nextel.com
| Email: MarvinToll@gtcGroup.com
| Web: http://www.gtcGroup.com
---------------------------------------------------------
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006q2@ryandesign.com]
Sent: Saturday, July 01, 2006 1:48 PM
To: MarvinToll@gtcGroup.com
Cc: 'Erik Huelsmann'; users@subversion.tigris.org
Subject: Re: Pessimistic Locking
> "Automatic Property Setting" capability can force the "needs-lock"
property to be set ...
Right. If you want *all* files to have svn:needs-lock, you can use
"*" to match all files regardless of extension.
Well note that auto-props are a client-side thing. There isn't really
any server-side property setting. So if you want a file (or all
files) to get the svn:needs-lock property, the only way it's going to
happen is if the user sets it on the file before committing it. To
make it automatic, the user would set up auto-props in their config
file. But since you can't force a user to use a particular config
file, they might forget, or intentionally not do it. So, if you still
want to enforce that every file in the repository has this property,
you would write and install a pre-commit hook that prevents anyone
from committing a file that doesn't have the property set. If they
try, you would output a helpful error message explaining that the
user should use auto-props to set this on all files, or even direct
them to a URL where they can download a recommended config file.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 1 20:50:40 2006