| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Template for commit messages |
| Date: | 2016-02-01 11:36:04 |
| Message-ID: | 20160201113604.GA8743@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-01-28 06:03:02 -0500, Bruce Momjian wrote:
> Reported-by:
> Bug:
> Author:
> Reviewed-by:
> Tested-by:
> Backpatch-through:
I personally, and I realize that I'm likely alone on that, would really
like to see references to relevant threads. A year after a commit or
such it often starts to get hard to know which threads a commit was
about. Often it's easy enough if it's about a single feature, but
bugfixes often originate in threads that have no directly corresponding
thread. And often the commit happens a while after there's been activity
in a thread. I spent days searching what thread "per discussion" in
commit messages refers to.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-01 11:53:56 | Re: Template for commit messages |
| Previous Message | Michael Paquier | 2016-02-01 11:29:52 | Re: Template for commit messages |