On Aug 31, 2015, at 11:39 AM, Stephan Beal <sgb...@googlemail.com> wrote: > > Hooks are not just about emails, but about policy decisions. "Does this file > conform to XYZ." A failure at that level is unrecoverable without changing > the policy.
I think we can agree that using hooks to enforce, say, code formatting rules is a bad idea. Now, maybe a hook could give a *warning* that you’ve just checked a C++ file in with tabs instead of spaces, but it shouldn’t refuse outright, because of the very risk you refer to. I’m going to guess that if you set hooks on a repo sitting behind “fossil server”, that those hook scripts don’t get sent down to a clone, or may not run of they do, so you can’t count on them being run locally before we get to the push stage? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
