| 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-08 00:25:38 |
| Message-ID: | 20190208002538.GG19742@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 07, 2019 at 12:20:35AM -0500, Tom Lane wrote:
> No, that'd be additional effort on top, which I'm not sure I see
> a reason for. Nobody's given a plausible reason why we need
> a machine-readable way to identify the bug reporter's name from
> the commit log. And we get a fair number of reports with no name
> or an obvious pseudonym, too, so how would you handle that?
Hm. Or just rely on Backpatch-through? A decent bug tracker usually
displays nicely what are the versions impacted, so this field should
be parsed anyway.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-08 00:37:40 | Re: Connection slots reserved for replication |
| Previous Message | Michael Paquier | 2019-02-08 00:23:42 | Re: Synchronize with imath upstream |