Re: bug tracking system

Поиск
Список
Период
Сортировка
Искать
От
Michael Paquier
Тема
Re: bug tracking system
Дата
Msg-id
20190208002538.GG19742@paquier.xyz
Ответ на
Список
Дерево обсуждения
bug tracking system Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: bug tracking system Alvaro Herrera <alvherre@2ndquadrant.com>
Re: bug tracking system Nathan Wagner <nw+pg@hydaspes.if.org>
Re: bug tracking system Alvaro Herrera <alvherre@2ndquadrant.com>
Re: bug tracking system Tom Lane <tgl@sss.pgh.pa.us>
Re: bug tracking system Alvaro Herrera <alvherre@2ndquadrant.com>
Re: bug tracking system Tom Lane <tgl@sss.pgh.pa.us>
Re: bug tracking system Michael Paquier <michael@paquier.xyz>
Re: bug tracking system Tom Lane <tgl@sss.pgh.pa.us>
Re: bug tracking system Michael Paquier <michael@paquier.xyz>
Re: bug tracking system Nathan Wagner <nw+pg@hydaspes.if.org>
Re: bug tracking system Tom Lane <tgl@sss.pgh.pa.us>
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
В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата:
От: Michael Paquier
Дата:
FAQ