[vtk-developers] New git commit hooks
david.gobbi at gmail.com
Fri Apr 23 10:43:42 EDT 2010
I have a quick question about commit messages. The pre-commit hook
tells me that the first line of the commit message must be 78 chars or
less, and the second line must be blank.
So how should commit messages be structured? A short descriptive
line, followed by a blank line, followed optionally by one or two
sentences giving details of the change?
On Fri, Apr 23, 2010 at 6:50 AM, Robert Maynard
<robert.maynard at kitware.com> wrote:
> On Fri, Apr 23, 2010 at 2:24 AM, Mark Olesen <Mark.Olesen at faurecia.com>
>> On Fri, 2010-04-23 at 10:34 +1000, Andrew Maclean wrote:
>> > I agree with you, I think that there also should be a commit check
>> > for tabs, otherwise layout gets really messy.
>> What about checking/stripping trailing whitespace as well?
>> This is something else that tends to look messy and result in lots of
>> noisy commits.
>> This electronic transmission (and any attachments thereto) is intended
>> solely for the use of the addressee(s). It may contain confidential or
>> legally privileged information. If you are not the intended recipient of
>> this message, you must delete it immediately and notify the sender. Any
>> unauthorized use or disclosure of this message is strictly prohibited.
>> Faurecia does not guarantee the integrity of this transmission and shall
>> therefore never be liable if the message is altered or falsified nor for any
>> virus, interception or damage to your system.
>> Powered by www.kitware.com
>> Visit other Kitware open-source projects at
>> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/Wiki/VTK/Git#Hooks Will show you how to copy the
> server commit checks for use on local commits.
> Robert Maynard
> Powered by www.kitware.com
> Visit other Kitware open-source projects at
> Follow this link to subscribe/unsubscribe:
More information about the vtk-developers