On Mon, Nov 6, 2017 at 5:00 PM, Tom Lane wrote:
> Magnus Hagander writes:
> > On Mon, Nov 6, 2017 at 4:46 PM, Tom Lane wrote:
> >> Hm, around here it's no match -> spam bucket. But in any case, why
>
> > I think you're quite
Magnus Hagander writes:
> On Mon, Nov 6, 2017 at 4:46 PM, Tom Lane wrote:
>> Hm, around here it's no match -> spam bucket. But in any case, why
> I think you're quite uncommon in that setup.
Interesting, because "it's not addressed to me (or any list
On Mon, Nov 6, 2017 at 4:46 PM, Tom Lane wrote:
> Magnus Hagander writes:
> > On Mon, Nov 6, 2017 at 4:40 PM, Tom Lane wrote:
> >> I suggest doing that the other way 'round. Otherwise, the email
> >> about the change will inevitably
Magnus Hagander writes:
> On Mon, Nov 6, 2017 at 4:40 PM, Tom Lane wrote:
>> 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
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost 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
On Mon, Nov 6, 2017 at 4:40 PM, Tom Lane wrote:
> Stephen Frost 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
Stephen Frost 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