Re: bug tracking system

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Nathan Wagner <nw+pg(at)hydaspes(dot)if(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: bug tracking system
Date: 2019-02-07 04:17:53
Message-ID: 20190207041753.GJ4074@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 06, 2019 at 10:50:51PM -0500, Tom Lane wrote:
> I do have a modest proposal for improving things going forward.
> How about, if a commit purports to fix a particular bug, that
> we say "Fixes: https://postgr.es/m/<message-id>" in place of
> our current habit of saying "Discussion: ...". For bugs that
> have come in through the bug form, the bug number is trivially
> extractable from the message-id these days; but this method
> works for any mailing list report, not just those.

Wouldn't it be the same as making the effort to have a proper
"Reported-by" field for each actual bug fix then? We already
have that attached to some of the commit logs for bug fixes. I
personally try to follow that pattern.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-02-07 04:34:15 Re: Add pg_partition_root to get top-most parent of a partition tree
Previous Message Michael Paquier 2019-02-07 04:12:23 Re: Inconsistent error handling in the openssl init code