From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, philmd@redhat.com, jian.j.wang@intel.com,
"rebecca@bluestop.org" <rebecca@bluestop.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Cc: "Ye, Ting" <ting.ye@intel.com>,
Stephano Cetola <stephano.cetola@intel.com>
Subject: Re: [edk2-devel] [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD
Date: Wed, 24 Apr 2019 21:17:00 +0200 [thread overview]
Message-ID: <11affcc6-4611-ea2c-4c1b-1a1986369f45@redhat.com> (raw)
In-Reply-To: <17b0c77c-cb9c-dbef-8101-889f2351f691@redhat.com>
+Stephano
On 04/24/19 11:25, Philippe Mathieu-Daudé wrote:
> On 4/22/19 3:46 PM, Wang, Jian J wrote:
>> crypto/uid.c is needed by VS201x toolchain on Windows. Let's still keep it in inf.
>> That means we need this patch for build on FreeBSD.
>>
>> Reviewed-by: Jian J Wang <jian.j.wang@intel.com>
>
> Commit 1a734ed85fda71630c795832e6d24ea560caf739 has weird authorship
> again: rebecca via Groups.Io <rebecca=bluestop.org@groups.io>
And, again, that's exactly how the sender is displayed to me by
Thunderbird, in my list folder only:
From: Rebecca via Groups.Io <rebecca=bluestop.org@groups.io>
Again, in email that I get directly from Rebecca, the From field looks
just fine.
So I don't think there's anything to fix for package maintainers here.
It seems that groups.io rewrites the sender address for Rebecca. I don't
know why groups.io performs this rewrite, and why only for Rebecca.
Stephano -- can you please ask groups.io why it keeps changing the From
header on messages sent by "Rebecca Cran <rebecca@bluestop.org>"?
Thanks
Laszlo
>
>> Jian
>>
>>> -----Original Message-----
>>> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>>> rebecca via Groups.Io
>>> Sent: Sunday, April 21, 2019 1:18 AM
>>> To: devel@edk2.groups.io; ard.biesheuvel@linaro.org
>>> Cc: Ye, Ting <ting.ye@intel.com>; Gang Wei <gang.wei@intel.com>; Wang, Jian
>>> J <jian.j.wang@intel.com>
>>> Subject: Re: [edk2-devel] [PATCH] CryptoPkg: add issetugid declaration to fix
>>> openssl build on FreeBSD
>>>
>>> On 2019-04-20 05:28, Ard Biesheuvel wrote:
>>>>
>>>> This is slightly odd. The host architecture shouldn't really matter,
>>>> and so if we end up calling different code in UEFI when built on *BSD,
>>>> there is differently something wrong. Or am I missing something?
>>>
>>>
>>> No, that's a good point. I guess it's something we don't ever call.
>>>
>>> In fact, OVMF continues to build after removing crypto/uid.c (which
>>> contains the OPENSSL_issetugid definition) from
>>> CryptoPkg/Library/OpensslLib/OpensslLib.inf and
>>> CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf .
>>>
>>>
>>> --
>>>
>>> Rebecca Cran
>
>
>
next prev parent reply other threads:[~2019-04-24 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 22:38 [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD rebecca
2019-04-20 11:28 ` [edk2-devel] " Ard Biesheuvel
2019-04-20 11:30 ` Ard Biesheuvel
2019-04-20 17:18 ` rebecca
2019-04-22 13:46 ` Wang, Jian J
2019-04-24 9:25 ` Philippe Mathieu-Daudé
2019-04-24 19:17 ` Laszlo Ersek [this message]
2019-04-24 19:29 ` rebecca
2019-04-24 19:36 ` rebecca
2019-04-25 1:06 ` Wang, Jian J
2019-04-26 13:55 ` rebecca
2019-04-26 13:56 ` Andrew Fish
2019-04-26 14:07 ` rebecca
2019-04-26 20:19 ` Laszlo Ersek
2019-04-27 0:06 ` rebecca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11affcc6-4611-ea2c-4c1b-1a1986369f45@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox