[vtk-developers] New git commit hooks

[Bill Lorensen]

But if the local commits are strict enough, (and include the master
hooks), they should be fine.

I think that most of us will agree that the more we can force
compliance through automation,  the better the software.

I hate to see us take a step backward.

Bill

On Fri, Apr 23, 2010 at 3:03 PM, Brad King <brad.king at kitware.com> wrote:
> Bill Lorensen wrote:
>> Why not keep the TAB check in both places. Even though the local hooks
>> are optional, developers will soon learn they should enable them
>> locally. Otherwise pushing will be a PITA.
>
> The concern is that some groups might keep a long-lived branch
> outside the main repository (using an online hosting site perhaps).
> When it comes time to merge that branch and push, one bad commit
> means the whole thing has to be rebased to fix the commit.  This
> creates trouble for those that continue to work on the branch
> because they will have to rebase their new work on the fixed-up
> branch.
>
> This is why we decided to make the update hook (push time) be
> strict only about history-breaking mistakes (like a bad email
> address).
>
> -Brad
>