From: "Andrew Fish" <afish@apple.com>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io, vit9696@protonmail.com,
Mike Kinney <michael.d.kinney@intel.com>,
"lersek@redhat.com" <lersek@redhat.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [PATCH v2 1/1] MdePkg: Add STATIC_ASSERT macro
Date: Fri, 16 Aug 2019 17:03:32 -0700 [thread overview]
Message-ID: <49AA4A1C-696C-478C-BECC-398B8B7A3534@apple.com> (raw)
In-Reply-To: <e4d9c7a8-5bc1-54fa-71bd-3aa4eff3706d@bsdio.com>
> On Aug 16, 2019, at 5:01 PM, Rebecca Cran <rebecca@bsdio.com> wrote:
>
> On 2019-08-16 16:58, Andrew Fish via Groups.Io wrote:
>>
>> I'm all for modernization of the C code as long we are thoughtful
>> about compatibility. For example I still see that VS2008 is a
>> supported BaseTools/Conf/tools_def.template.
>
>
> It would be interesting to see who's using the older toolchains against
> current/newer revisions of the edk2.
>
> For example at work we build a UEFI driver using VS2012, but it's
> against the UDK2014.SP1 branch, and being for a legacy product we'll
> never migrate to a newer UDK release or master tag.
>
Rebecca,
It is also interesting in the context of our CI as we could pick oldest and newest version from every compiler family for the CI build test.
Thanks,
Andrew Fish
>
> --
> Rebecca Cran
>
next prev parent reply other threads:[~2019-08-17 0:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 8:16 [PATCH v2 0/1] MdePkg: Add STATIC_ASSERT macro vit9696
2019-08-13 8:16 ` [PATCH v2 1/1] " vit9696
2019-08-14 13:50 ` [edk2-devel] " Liming Gao
2019-08-14 15:47 ` Michael D Kinney
2019-08-14 16:22 ` Vitaly Cheptosv
2019-08-15 1:05 ` Yao, Jiewen
2019-08-15 1:59 ` Liming Gao
2019-08-15 2:22 ` Vitaly Cheptosv
2019-08-15 7:36 ` Yao, Jiewen
2019-08-16 16:33 ` Laszlo Ersek
2019-08-16 17:23 ` Vitaly Cheptsov
2019-08-16 19:38 ` Laszlo Ersek
2019-08-16 20:19 ` Laszlo Ersek
2019-08-16 21:04 ` Michael D Kinney
2019-08-16 21:40 ` Vitaly Cheptsov
2019-08-16 22:23 ` rebecca
2019-08-16 22:58 ` Andrew Fish
2019-08-16 23:34 ` Vitaly Cheptsov
2019-08-17 0:01 ` rebecca
2019-08-17 0:03 ` Andrew Fish [this message]
2019-08-17 0:09 ` rebecca
[not found] ` <15BB8D3E51450F1C.5853@groups.io>
2019-08-21 21:41 ` rebecca
2019-08-16 21:32 ` Vitaly Cheptsov
2019-08-16 16:28 ` Laszlo Ersek
2019-08-15 16:08 ` Michael D Kinney
2019-08-16 19:40 ` Laszlo Ersek
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=49AA4A1C-696C-478C-BECC-398B8B7A3534@apple.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