From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>, 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-02 03:15:35 |
Message-ID: | 20160202031535.GA4095668@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 01, 2016 at 01:55:23PM +0200, Heikki Linnakangas wrote:
> On 01/02/16 13:36, Andres Freund wrote:
> >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.
>
> +1. I also quite often look at a commit message, and then hunt the "per
> discussion". A message-id would save some time there.
+1
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-02-02 03:18:14 | Re: Support for N synchronous standby servers - take 2 |
Previous Message | Michael Paquier | 2016-02-02 03:01:36 | Re: Several problems in tab-completions for SET/RESET |