SteveKing <steveking@gmx.ch> writes:
> >>both options won't make our users very happy. Especially if you think
> >>about the hook script won't be used by much repo admins (considering
> >>they have to update their server first), also many projects will be
> >>happy with static templates and don't need the magic hook script.
> > Are you sure? Consider the 'pre-revprop-change' hook. I think most
> > repositories set that up, so people can change commit messages, and
> > yet it is *not* enabled by default.
>
> The 'pre-revprop-change' hook isn't something that is called by the
> client *before* the actual commit. So the authentication has to be
> done only once (see my timing considerations above), and it has to be
> done anyway so the added time isn't even noticed by the user.
I think Karl was offering a rebuttal to "won't be used by much repo
admins", not talking about timing costs of using the hook.
He points out that most admins actually go through extra efforts to
turn on the pre-revprop-change hook (because the default state is to
disallow that functionality), so there's no reason to believe they
wouldn't go through similar extra efforts to turn on the
pre-commit-gimme-a-funky-template hook. Therefore, he thinks the new
hook *will* be used by "much repo admins".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 27 20:57:11 2005