Re: post-commit script to set keywords/prop-set hit and miss

On Wed, Dec 01, 2004 at 10:10:44PM -0600, Ben Collins-Sussman wrote:
>
> On Dec 1, 2004, at 6:51 PM, Jennifer Kesterson wrote:
>
> > We wrote a post-commit hook script to set keywords and EOL styles in
> >the current repository on files that don't have them set.
>
> Yikes, this is a *really bad* strategy.

And you're going to continue to see people attempt it until server-side
default properties are available.

Yes, I've read the relevant entry in the issue tracker, I understand
that there are non-trivial issues to be solved, and no, I don't have the
time to contribute it. I'm not try to criticize here, just explain why
this pops up on a regular basis: trying to enforce a consistent set of
client configurations across a large and/or diverse set of developers
is difficult, especially if those configurations change over time, or
are different for different projects/repositories.

It might be worth adding a big warning and
explanation to the "post-commit" hook entry in
http://svnbook.red-bean.com/en/1.0/ch05s02.html#svn-ch-5-sect-2.1.

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org