Hi Armin,
On Sun, 09 Oct 2016 20:29:39 akuster808 wrote:
> On 10/09/2016 05:35 PM, Paul Eggleton wrote:
> > I've been going through the commits in preparation for our release notes,
> > and unfortunately what I'm seeing is that the number of empty or
> > incomplete commit messages has noticeably i
Paul,
On 10/09/2016 05:35 PM, Paul Eggleton wrote:
Hi folks,
I've been going through the commits in preparation for our release notes, and
unfortunately what I'm seeing is that the number of empty or incomplete commit
messages has noticeably increased over previous releases. Commit messages a
Hi folks,
I've been going through the commits in preparation for our release notes, and
unfortunately what I'm seeing is that the number of empty or incomplete commit
messages has noticeably increased over previous releases. Commit messages are
vitally important to providing a readable history,
There appears to be a general trend towards short commit messages. I
don't impose a "must have a long log and short log" policy but I'll have
to if things don't improve.
To be clear, the commit message needs to say not just what changed but
*why* the change is necessary, e.g. what error it causes
