From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8E06E210C1254 for ; Tue, 24 Jul 2018 05:39:19 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D6233401EF05; Tue, 24 Jul 2018 12:39:18 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-190.rdu2.redhat.com [10.10.120.190]) by smtp.corp.redhat.com (Postfix) with ESMTP id 62F622166BA0; Tue, 24 Jul 2018 12:39:18 +0000 (UTC) To: =?UTF-8?Q?Marvin_H=c3=a4user?= , "edk2-devel@lists.01.org" References: <4aaed815-a16d-a6b9-ddd5-f941ea48b22c@redhat.com> From: Laszlo Ersek Message-ID: <7728cda6-976f-0b89-120c-1ca540a02c33@redhat.com> Date: Tue, 24 Jul 2018 14:39:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Tue, 24 Jul 2018 12:39:18 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Tue, 24 Jul 2018 12:39:18 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:'' Subject: Re: [PATCH 7/8] OvmfPkg/SmmAccessPei: Update MM PPI usages. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 12:39:20 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit On 07/24/18 14:16, Marvin Häuser wrote: > Hey Laszlo, > >> -----Original Message----- >> (1) Please post patch sets using a cover letter message: >> >> git config format.coverletter true >> git config format.numbered true >> git config sendemail.chainreplyto false >> git config sendemail.thread true >> >> Otherwise the individual patches in the series will get intermixed with other >> messages / threads on the mailing list (and in people's inboxes), if the >> recipient uses a threaded view in their MUA (which most people should do -- >> patches and discussions are very hard to follow otherwise). > > Is V2 fine in this aspect? Outlook has never threaded multiple parts of a patch series for me but only replies to their original message, hence I did not notice something was off. It doesn't look right to me, looking at the following patches patches: [edk2] [PATCH v2 0/2] Introduce UEFI PI 1.5 MM PPI. [edk2] [PATCH v2 1/2] MdePkg: Add PI 1.5 MM PPI declarations. [edk2] [PATCH v2 2/2] MdeModulePkg: Change SMM PPIs to shim MM PPIs. * v2 0/2: Message-ID: * v2 1/2: Message-ID: References: In-Reply-To: * v2 2/2: Message-ID: References: In-Reply-To: Here's what I think happened: the original message-id (formatted by your local tooling) for the cover letter was Accordingly, your local tools placed this message ID *correctly* into both "In-Reply-To" and "References" headers of the actual patches #1 and #2. This is the proper way to ensure threading. Unfortunately, outlook.com's SMTP server seems to have overwritten your Message-ID, on the cover letter (and the rest of the emails too), despite your tools generating and embedding Message-ID in the first place. Obviously this breaks threading. This is a bug in outlook.com's SMTP service, most likely. Can you open a support ticket with them, or else use something else for posting patches than outlook.com? Thanks, Laszlo