| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:36:50 |
| Message-ID: | 56AA3592.6040500@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-01-28 15:39:00 | Re: Template for commit messages |
| Previous Message | David Fetter | 2016-01-28 15:32:52 | Re: Template for commit messages |