From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web12.8657.1587049977487996616 for ; Thu, 16 Apr 2020 08:12:57 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QDW+nZtX; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587049976; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5NXHqzu32/5szKotp6xZbszXtlQuQEK4vQ349Z9/D40=; b=QDW+nZtXBmJv9P8TAzufxXuFcWzaWejTm6osUmNXWocpQWJkyXetRp+X4Jd6b32H7EH3kj 5ZR86srgswzdMv40Ak4O+/BxQhydgqBWd7L5o6khovlrBjeWEvZC/8aW5da7yOO1jBmAYU Oskc+cZKjGJPzF8QZMQYenyFL53mLoE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-465-pnYgTwKQMfC5u2x8oWuYyw-1; Thu, 16 Apr 2020 11:12:50 -0400 X-MC-Unique: pnYgTwKQMfC5u2x8oWuYyw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 11C17107ACC9; Thu, 16 Apr 2020 15:12:49 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-225.ams2.redhat.com [10.36.114.225]) by smtp.corp.redhat.com (Postfix) with ESMTP id 10A7D5D9E2; Thu, 16 Apr 2020 15:12:47 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH v1 2/6] ArmVirtPkg: Add Platform CI and configuration for Core CI To: Sean , devel@edk2.groups.io References: <78837035-1a4c-2518-622f-0d898752f6d3@redhat.com> <31845.1586979078724820005@groups.io> Cc: Ard Biesheuvel , Bret Barkelew From: "Laszlo Ersek" Message-ID: Date: Thu, 16 Apr 2020 17:12:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <31845.1586979078724820005@groups.io> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Sean, On 04/15/20 21:31, sean.brogan via [] wrote: > My corporate mail server changes the subject line which also destroys > threading so I figured this was better. Maybe not as i have no > control over the CC/To lines of the email that is sent. Do Bret's > responses which add "[External]" (example here: > https://edk2.groups.io/g/devel/message/57377) ( > https://edk2.groups.io/g/devel/message/57377 ) to every reply show up > better (in groups.io web ui this is harder to follow since it starts > a new thread)? Thank you very much for providing Bret's email as an example! Bret's answers in that thread, namely: https://edk2.groups.io/g/devel/message/57377 https://edk2.groups.io/g/devel/message/57381 are well-threaded. Both in my personal list folder, as presented by my MUA (Thunderbird), and also in e.g. the following (secondary) mailing list archive: http://mid.mail-archive.com/CY4PR21MB074349715A82905EB420D7DBEFDA0@CY4PR21MB0743.namprd21.prod.outlook.com http://mid.mail-archive.com/CY4PR21MB07431322730AF342BF898A74EFDA0@CY4PR21MB0743.namprd21.prod.outlook.com If you open each one of those "mail-archive.com" links in separate browser windows or tabs, and scroll to the bottom of both pages, you'll see that Bret's answer's are correctly threaded against the rest of the messages in that discussion. The subject line is not directly relevant for threading. Some MUAs use the subject as a fallback option for reconstructing threads, but the primary linkage for threading is the In-Reply-To header of the response email -- which is supposed to reference the Message-Id header of the original email. So, for example, Rebecca's thread starter carried the header Message-ID: <62933ee8-7fb9-7cd3-08e5-6d6e7dac31e9@bsdio.com> and Bret's reply correctly carried the header In-Reply-To: <62933ee8-7fb9-7cd3-08e5-6d6e7dac31e9@bsdio.com> It doesn't matter (for threading) that Bret's infrastructure changed the subject. Sometimes people intentionally change the subject line, while staying in the same thread -- that signals that they go off on a tangent, but still want to stay on topic a little (or else they want to preserve the linkage to the original discussion). For example, the original subject could be foo bar Re: foo bar Re: foo bar and then someone could go off on a tangent (in the same thread!) like this: quux [was: foo bar] Re: quux [was: foo bar] So while the "[External]" stuff is not particularly useful or welcome, regarding the list traffic, it is not a deal breaker. The threading does remain correct. If the groups.io WebUI loses track of threading just because of subject line changes, then that's a groups.io WebUI bug. Bret's MUA also seems to correctly preserve CC's -- Rebecca's thread starter CC'd Bob and Liming, and Bret's responses carry those CC's too. If you could adopt Bret's way of interacting with the list, I think that would be great! Thanks! Laszlo