From: Jakub Narebski <jnareb@gmail.com>
Date: Mon, 25 Apr 2011 10:45:03 GMT
Subject: Re: Dates in Commits and other issues of style (Re: [RFC 2/5] Pretty Print: show tz when using DATE_LOCAL)
Message-ID: <m3bozuwqyz.fsf@localhost.localdomain>
In-Reply-To: <7vhb9nkmo1.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Enforcing consistency is one of the important tasks the maintainers do in
> their projects.  Besides ensuring that the intent of the change each patch
> brings to the codebase is good, that the log entry describes the change in
> a useful way for future readers, and that the patch correctly implements
> the described change, we also need to make sure that the resulting code
> matches the style of the surrounding code, and the style, structure and
> tone the log messages are delivered in a consistent voice.  Otherwise it
> would quickly get very tiring when you have to dig into the history of the
> codebase.  The code and the history are read a lot more often than are
> written. [...]

This information should be put e.g. in SubmittingPatches, or
CodingGuidelines, or MaintNotes, isn't it?

-- 
Jakub Narebski
Poland
ShadeHawk on #git