Re: Schedule for migration to pglister - Mailing list pgsql-hackers

From Justin Clift
Subject Re: Schedule for migration to pglister
Date
Msg-id 096cef2c98e890dc30cdc905ff962d25@postgresql.org
Whole thread Raw
In response to Re: Schedule for migration to pglister  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Schedule for migration to pglister  (Magnus Hagander <magnus@hagander.net>)
Re: Schedule for migration to pglister  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 2017-11-16 15:34, Stephen Frost wrote:
> Magnus, all,
> 
> * Magnus Hagander (magnus@hagander.net) wrote:
>> mbox access should now be restored, and as Stephen says, now handled 
>> by the
>> Date in the message. Let me know if there are any issues with the new 
>> ones.
>> (They're now generated by the same code as the per-thread ones).
> 
> And just fyi, that also means that complete threads end up in each 
> mbox,
> so you'll see cases where a message was posted to, eg, -committers
> initially but the reply cc'd hackers, bringing the thread over there,
> and now the initial email to -committers and all of the subsequent
> emails on the thread will be included in the mbox for both -hackers and
> -committers.
> 
> Hopefully everyone finds that to actually provide a better experience,
> but it's a difference to be aware of.

In theory :), that sounds better for people reading the web archives.

Only one real way to find out "for sure" though, so fingers crossed. :)

+ Justin



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PROPOSAL] Temporal query processing with range types
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] A weird bit in pg_upgrade/exec.c