From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Kam Lasater <ckl(at)seekayel(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: No Issue Tracker - Say it Ain't So! |
Date: | 2015-10-01 17:25:30 |
Message-ID: | 560D6C8A.5020608@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/01/2015 05:10 PM, Andres Freund wrote:
> On 2015-10-01 11:07:12 -0400, Tom Lane wrote:
>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>> On 2015-10-01 16:48:32 +0200, Magnus Hagander wrote:
>>>> That would require people to actually use the bug form to submit the
>>>> initial thread as well of course - which most developers don't do
>>>> themselves today. But there is in itself nothing that prevents them from
>>>> doing that, of course - other than a Small Amount Of Extra Work.
>>
>>> It'd be cool if there were a newbug@ or similar mail address that
>>> automatically also posted to -bugs or so.
>>
>> I believe that's spelled pgsql-bugs(at)postgresql(dot)org(dot)
>
> The point is that newbug would automatically assign a bug id, without
> going through the form.
if we only want that - we can trivially implement that on the mailserver
side by asking the backend database sequence for a bugid and rewriting
the subject...
But given debbugs is on the radar not sure we need it...
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-10-01 18:12:40 | Re: max_worker_processes on the standby |
Previous Message | Josh Berkus | 2015-10-01 17:09:35 | Re: No Issue Tracker - Say it Ain't So! |