Re: pgsql: Remove references to Majordomo - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pgsql: Remove references to Majordomo
Date
Msg-id CABUevEx8o6wSkUdegr8AX0-uCqDhW9zkeU6-1yPUypcsVJ-9Gg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Remove references to Majordomo  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pgsql: Remove references to Majordomo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Sat, Jan 19, 2019 at 7:19 PM Stephen Frost <sfrost@snowman.net> wrote:
Greetings,

* Magnus Hagander (magnus@hagander.net) wrote:
> On Fri, Jan 18, 2019 at 4:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Magnus Hagander <magnus@hagander.net> writes:
> > > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier <michael@paquier.xyz>
> > wrote:
> > >> Wouldn't it be better to also switch the references to pgsql-bugs in
> > >> all the C code for the different --help outputs?
> >
> > > You are right, we definitely should. I'll go ahead and fix that. I can't
> > > quite make up my mind on if it's a good idea to backpatch that though --
> > > it's certainly safe enough to do, but it might cause issues for
> > translators?
> >
> > Yeah, weak -1 for back-patching.  We don't usually like to thrash
> > translatable messages in the back branches.
>
> Pushed.

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.

--

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pgsql: Remove references to Majordomo
Next
From: Michael Meskes
Date:
Subject: Re: Thread-unsafe coding in ecpg