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

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

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-12-02 05:10:44 CET

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.

   - What's preventing infinite loops? If your post-commit hook does
another commit, does the resulting commit call the post-commit hook

   - Every time a user commits, they have to 'update' again, because
they're immediately out of date. Bleh.

Instead, you should be making your users use 'auto-props' from their
clients, and if that's not enough, you should be using a *pre-commit*
hook to reject commits that don't set properties. Please read this


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 2 05:12:58 2004

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.