| From: | Justin Clift <justin(at)postgresql(dot)org> | 
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> | 
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> | 
| Subject: | Re: Schedule for migration to pglister | 
| Date: | 2017-11-16 15:51:41 | 
| Message-ID: | [email protected] | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers pgsql-www | 
On 2017-11-16 15:34, Stephen Frost wrote:
> Magnus, all,
> 
> * Magnus Hagander (magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-16 16:20:02 | Re: [HACKERS] A weird bit in pg_upgrade/exec.c | 
| Previous Message | Robert Haas | 2017-11-16 15:42:35 | Re: [HACKERS] [PROPOSAL] Temporal query processing with range types | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-11-16 21:37:21 | Re: Schedule for migration to pglister | 
| Previous Message | Stephen Frost | 2017-11-16 15:34:06 | Re: Schedule for migration to pglister |