On Sat, Feb 2, 2019 at 9:18 AM Noah Misch wrote:
> On Mon, Jan 28, 2019 at 07:29:39PM +0100, Magnus Hagander wrote:
> > On Mon, Jan 28, 2019 at 7:26 PM Tom Lane wrote:
> > > Stephen Frost writes:
> > > >> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch
> wrote:
> > > >>> What are those blocked infr
On Mon, Jan 28, 2019 at 07:29:39PM +0100, Magnus Hagander wrote:
> On Mon, Jan 28, 2019 at 7:26 PM Tom Lane wrote:
> > Stephen Frost writes:
> > >> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch wrote:
> > >>> What are those blocked infrastructure improvements?
> >
> > > The specific improvements we
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Mon, Jan 28, 2019 at 7:26 PM Tom Lane wrote:
>
> > Stephen Frost writes:
> > >> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch wrote:
> > >>> What are those blocked infrastructure improvements?
> >
> > > The specific improvements we're
On Mon, Jan 28, 2019 at 7:26 PM Tom Lane wrote:
> Stephen Frost writes:
> >> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch wrote:
> >>> What are those blocked infrastructure improvements?
>
> > The specific improvements we're talking about are DKIM/DMARC/SPF, which
> > is becoming more and more im
Stephen Frost writes:
>> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch wrote:
>>> What are those blocked infrastructure improvements?
> The specific improvements we're talking about are DKIM/DMARC/SPF, which
> is becoming more and more important to making sure that the email from
> our lists can ac
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Sun, Jan 27, 2019 at 2:28 AM Noah Misch 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..?
> > >
> > > I can understand
On Sun, Jan 27, 2019 at 2:28 AM Noah Misch 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..?
> >
> > I can understand the concern around translators and back-patching and
> > such, but I
On Sat, Jan 19, 2019 at 01:19:46PM -0500, Stephen Frost wrote:
> * Magnus Hagander (mag...@hagander.net) wrote:
> > On Fri, Jan 18, 2019 at 4:02 PM Tom Lane wrote:
> > > Magnus Hagander writes:
> > > > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier
> > > wrote:
> > > >> Wouldn't it be better to
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Magnus Hagander writes:
> > On Sat, Jan 19, 2019 at 7:19 PM Stephen Frost 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..?
>
> >
Magnus Hagander writes:
> On Sat, Jan 19, 2019 at 7:19 PM Stephen Frost 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
On Sat, Jan 19, 2019 at 7:19 PM Stephen Frost wrote:
> Greetings,
>
> * Magnus Hagander (mag...@hagander.net) wrote:
> > On Fri, Jan 18, 2019 at 4:02 PM Tom Lane wrote:
> > > Magnus Hagander writes:
> > > > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier >
> > > wrote:
> > > >> Wouldn't it be
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Fri, Jan 18, 2019 at 4:02 PM Tom Lane wrote:
> > Magnus Hagander writes:
> > > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier
> > wrote:
> > >> Wouldn't it be better to also switch the references to pgsql-bugs in
> > >> all the C c
On Fri, Jan 18, 2019 at 4:02 PM Tom Lane wrote:
> Magnus Hagander writes:
> > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier
> 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 definite
On Fri, Jan 18, 2019 at 10:02:47AM -0500, Tom Lane wrote:
> Magnus Hagander writes:
>> 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
Magnus Hagander writes:
> On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier 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
On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier wrote:
> On Thu, Jan 17, 2019 at 01:04:44PM +, Magnus Hagander wrote:
> > Remove references to Majordomo
> >
> > Lists are not handled by Majordomo anymore and haven't been for a while,
> > so remove the reference and instead direct people to th
On Thu, Jan 17, 2019 at 01:04:44PM +, Magnus Hagander wrote:
> Remove references to Majordomo
>
> Lists are not handled by Majordomo anymore and haven't been for a while,
> so remove the reference and instead direct people to the list server.
Wouldn't it be better to also switch the reference
17 matches
Mail list logo
