| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Maciek Sakrejda <maciek(at)heroku(dot)com> |
| Subject: | Re: Fwd: [Still Failing] pg-quilter/postgres#111 (master - 82b0102) |
| Date: | 2013-07-04 00:54:16 |
| Message-ID: | CAM3SWZQboGoVYAJNoPMx=uDLE+Zh5k2MQa4dWk91YPGDxuY-gQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 3, 2013 at 5:36 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Does anyone know why I received the message below, or how to turn it off?
>
> Sending out notifications such as this (bogus in this case anyway) is
> unfriendly.
This was an oversight. I'm sorry you were affected in this way.
My colleague Maciek Sakrejda is working on a tool that monitors
pgsql-hackers and ultimately structures patches as pseudo pull
requests on a mirror of Postgres on Github. This includes doing things
like running the regression tests via travis CI.
Since the cat is now out of the bag before we managed to iron out some
outstanding issues, you might as well look at the github page:
https://github.com/deafbybeheading/pg-quilter
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-07-04 01:11:10 | Re: event trigger API documentation? |
| Previous Message | Andrew Dunstan | 2013-07-04 00:36:45 | Fwd: [Still Failing] pg-quilter/postgres#111 (master - 82b0102) |