From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bugs and bug tracking |
Date: | 2015-10-07 17:25:51 |
Message-ID: | 20151007172551.GD4405@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> > If you want such an API, I won't stop you from using it, but I will not
> > use it myself. Please put in message-body commands as well.
>
> So, unsurprisingly, debbugs does support all commands that can be sent
> to control@ also through the NNN(at)bugs(dot)postgresql(dot)org system; the command
> simply needs to be prefixed with 'Control: ' and then '-1' can be used
> as the bug number (so you don't have to figure out what the right number
> is, etc), like so:
>
> Control: close -1
> Control: tags -1 wontfix
Supposedly we will want our traffic to still flow via
pgsql-bugs(at)postgresql(dot)org, so the trick of grabbing the bug number from
the To address will not be available, will it?
Hmm, I guess we could have the bug form add
To: NNN(at)bugs(dot)postgresql(dot)org
CC: pgsql-bugs(at)postgresql(dot)org
as headers, which should work for most people (since we reply-all), Josh
Berkus being the exception.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2015-10-07 17:30:01 | Re: Small documentation fix in src/interfaces/ecpg/preproc/po/pt_BR.po |
Previous Message | Stephen Frost | 2015-10-07 17:20:13 | Re: bugs and bug tracking |