From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Remove references to Majordomo |
Date: | 2019-01-21 17:00:31 |
Message-ID: | 20190121170031.GY2528@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Greetings,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Sat, Jan 19, 2019 at 7:19 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> >> Does this also implicitly mean we've just agreed to push back the
> >> retirement of the @postgresql.org aliases for the lists until v11 is
> >> EOL..?
>
> > Specifically for pgsql-bugs, yes :) We can special-case that one when the
> > time comes, and retire the other ones properly.
That might possibly work.
> If you're hoping to wait till nobody's copy of Postgres mentions the
> @postgresql.org addresses, you're going to be waiting a long time.
I was thinking that we would want to make sure that supported versions
have the correct address, but if we're fine with special-casing the old
aliases and keeping them working, as Magnus suggests, then I suppose it
doesn't matter.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-01-21 17:07:09 | pgsql: Avoid thread-safety problem in ecpglib. |
Previous Message | Tom Lane | 2019-01-21 16:30:11 | pgsql: Revert "Fix under-quoted filename pattern in pgbench TAP test." |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2019-01-21 17:07:56 | Re: House style for DocBook documentation? |
Previous Message | Chapman Flack | 2019-01-21 16:46:05 | Re: House style for DocBook documentation? |