From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Schedule for migration to pglister |
Date: | 2017-11-06 15:42:49 |
Message-ID: | CABUevEwXX5Fjv-PyZk_bw4q41HwJ7t3RSu4bcmx84i-EAR=KhQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On Mon, Nov 6, 2017 at 4:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > Each list will receive an email with a link to the wiki about the
> > migration after the list has been migrated.
>
> I suggest doing that the other way 'round. Otherwise, the email
> about the change will inevitably go into a lot of peoples' bit
> buckets if they haven't adjusted their mail filters yet.
>
The argument for doing it after the migration is that the complaints that
we have received so far have all been from people where email ends up in
the *inbox* after the migration, not the bitbucket. That's the default
action in most peoples MUAs when their rules no longer match...
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-11-06 15:43:15 | Re: Schedule for migration to pglister |
Previous Message | Tom Lane | 2017-11-06 15:40:16 | Re: Schedule for migration to pglister |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-11-06 15:43:15 | Re: Schedule for migration to pglister |
Previous Message | Tom Lane | 2017-11-06 15:40:16 | Re: Schedule for migration to pglister |