[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

start-commit to enforce needs-lock?

From: A. M. Passy <amarcpassy_at_gmail.com>
Date: 2007-08-07 17:14:22 CEST

I'm looking for a way to enforce the setting of the svn:needs-lock
property for new and imported files. I've read the appropriate
sections of the svnbook and read a whole lot of the mailing list
traffic. I understand that using a pre-commit hook is considered bad,
because one is modifying an in-process transaction (though as an
aside, no one has explained exactly under what conditions, i.e._why_
it is bad - the comments are all in the mode of "there be dragons").

But I notice that there is the "start-commit" hook, which happens
before the transaction is created. What's wrong with adding the
property if not present at that point?

BTW - I've read all the arguments for the supported models of source
control, Lock-Modify-Unlock, and Copy-Modify-Merge, and for reasons
that mainly relate to our userbase, we're going with the
Lock-Modify-Unlock model.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 7 17:12:44 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.