Re: Template for commit messages

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: 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-28 15:40:09
Message-ID: 20160128154009.GQ3331@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Joshua D. Drake (jd(at)commandprompt(dot)com) wrote:
> On 01/28/2016 06:57 AM, Robert Haas wrote:
>
> >>I'm on board with Bruce's template as being a checklist of points to be
> >>sure to cover when composing a commit message. I'm not sure we need
> >>fixed-format rules.
> >
> >Well, I think what people are asking for is precisely a fixed format,
> >and I do think there is value in that. It's nice to capture the
> >nuance, but the nuance is going to get flattened out anyway when the
> >release notes are created. If we all agree to use a fixed format,
> >then a bunch of work there that probably has to be done manually can
> >be automated. However, if we all agree to use a fixed format except
> >for you, we might as well just forget the whole thing, because the
> >percentage of commits that are done by you is quite high.
>
> Yes, we are either all in or we may as well forgo this.

I don't have a particular issue with it, but would like whatever
template is decided upon to be included in our git repo and then we
should be able to make it the template that's opened up when people go
to commit pretty easily.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2016-01-28 15:50:59 Re: CustomScan under the Gather node?
Previous Message Joshua D. Drake 2016-01-28 15:39:00 Re: Template for commit messages