Re: Template for commit messages

From: Andres Freund <andres(at)anarazel(dot)de>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Template for commit messages
Date: 2016-01-29 09:53:21
Message-ID: 20160129095122.ihusxsebf2wjiafe@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-01-29 04:42:08 -0500, Bruce Momjian wrote:
> On Thu, Jan 28, 2016 at 07:30:58PM -0500, Andrew Dunstan wrote:
> > I have no prejudice in this area, other than one in favor of any
> > rules being fairly precise. As for nuances, I guess they can be
> > specified in the commit message. The one thing I do find annoying
> > from time to time is the limit on subject size. Sometimes it's very
> > difficult to be sufficiently communicative in, say, 50 characters.
>
> Agreed, but that is a gitweb limit we can't control, I think.

That's not that hard to change. And neither git nor kernel people use 50
char limits. I'm *strongly* opposed to making 50 chars the limit for the
first line.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2016-01-29 10:09:53 Re: WIP: Access method extendability
Previous Message Bruce Momjian 2016-01-29 09:42:08 Re: Template for commit messages