On 5/4/23 10:20, Gavin Lambert via Boost wrote:
On 4/05/2023 18:34, Julien Blanc wrote:
You're luckier than me. The current thread is semi-broken, but the "replacing the ML with a forum" one is completely broken for me.
Sorry, that was sloppy reporting on my part. There was a large tree of posts that were all together so I foolishly assumed that this was the whole thread.
There were *also* a bunch of disconnected replies earlier on, but since these were completely disconnected they didn't "follow" the parent higher in the list since I'm sorting by date. This meant they were out of sight at the time I was thinking about this and writing my message.
I'm starting to wonder if we all receive the same emails (in the sense that they may not contain the same set of headers). For me, the initial message of Vinnie in the "replacing the ML with a forum" thread contains the following:
Message-ID: <010f0187bde5599a-e76c27f2-225d-4d7e-b2c8-887e3a07ecb8-000000@us-east-2.amazonses.com>
But Mashshall's answer, on the other side, contains the following headers :
References: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com> In-Reply-To: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com>
The "In-Reply-To" should match the Id of the initial message, for threading to work correctly. This is too obvious to be a client bug. Can someone check the Message-ID he has for the initial message of Vinnie in the "replacing the ML with a forum" thread? If it's different from mine, then that's probably the source of the issues.
For me (via gmane), Vinnie's original message has:
Message-ID: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000@us-east-2.amazonses.com>
And Marshall's reply (did not thread properly) has:
Message-ID: <010f0187bde8bc2e-bebb94d1-2dfb-4165-ad8d-6af8e9b41381-000000@us-east-2.amazonses.com> References: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com> In-Reply-To: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com>
Robert's reply (did thread properly) has:
Message-ID: <010f0187bf4b951d-1f6d7af8-3f2e-458b-9ffd-ca91ecfe04f9-000000@us-east-2.amazonses.com> References: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000@us-east-2.amazonses.com> In-Reply-To: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000@us-east-2.amazonses.com>
These do indeed seem to be different from yours, which is unfortunate.
It would be good if someone else not using gmane could check both results as well (although that shouldn't be a factor, as I have other groups that don't appear to be getting flattening).
I'm reading the ML in Thunderbird. Vinnie's initial message has: Message-ID: <010f0187bde531b6-2cd00e40-57e1-476f-b30d-896ff8eab806-000000@us-east-2.amazonses.com> Marshall's reply: References: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com> In-Reply-To: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000@us-east-2.amazonses.com> Message-ID: <010f0187bde8ccef-31042da0-3d20-4f4a-95e8-74cd3770cc89-000000@us-east-2.amazonses.com> Robert's reply: Message-ID: <010f0187bf4ba591-77f55894-1b8b-40d4-b8ac-0d6af2b9ba6d-000000@us-east-2.amazonses.com> References: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000@us-east-2.amazonses.com> In-Reply-To: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000@us-east-2.amazonses.com> For me, both Marshall's and Robert's replies, which are direct replies to the initial Vinnie's post, start their own threads with their subtrees of replies. The only descendant of the Vinnie's initial post is my own reply to it, which has this: Message-ID: <187be1c7608.280f.fb49792bc380c7e55e30f872b414f11c@gmail.com> In-Reply-To: <010f0187bde531b6-2cd00e40-57e1-476f-b30d-896ff8eab806-000000@us-east-2.amazonses.com> References: <010f0187bde531b6-2cd00e40-57e1-476f-b30d-896ff8eab806-000000@us-east-2.amazonses.com> So basically, every direct reply to the original post, except my own one, is a separate subtree (or a single out-of-tree message if there were no replies to it).