[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vtk-developers
Subject:    Re: [vtk-developers] [Paraview-developers]  New git commit hooks
From:       Brad King <brad.king () kitware ! com>
Date:       2010-04-26 14:01:21
Message-ID: 4BD59CB1.6000403 () kitware ! com
[Download RAW message or body]

Moreland, Kenneth wrote:
> Veering slightly off the main topic, could we get some guidance on the
> minutia that we are expected to follow when coding and committing
> changes to VTK, ParaView, etc.?  Many of the details are undocumented
> and I (and probably everyone else) have been relying on the CVS
> pre-commit checks (and now git commit/push hooks) to guide me.
> 
> Where the git hooks deviate from the CVS checks (and they deviate in
> almost every possible way) I assumed that the commit rules were being
> updated.  For example, I have already stopped using those BUG/ENH/PERF
> prefixes to many of my commit descriptions figuring that we were moving
> to a more standard git-style description.

I've updated the documentation of the local hooks to describe what they
check and how to format commit messages:

  http://www.vtk.org/Wiki/VTK/Git#Hooks

(and how to update them as more changes are made).

I'll try to get to the TODO in that block and document the server-side
checks soon.

-Brad
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.vtk.org/mailman/listinfo/vtk-developers

[prev in list] [next in list] [prev in thread] [next in thread]