From: Andrew Fish <afish@apple.com>
To: Mike Kinney <michael.d.kinney@intel.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
"Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Cetola, Stephano" <stephano.cetola@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [RFC] Proposal to remove DuetPkg
Date: Tue, 20 Nov 2018 16:59:24 -0800 [thread overview]
Message-ID: <4108E983-A970-4530-B8B2-9F0FEEEABCFA@apple.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8B331EA@ORSMSX113.amr.corp.intel.com>
Works for me too.
Thanks,
Andrew Fish
> On Nov 20, 2018, at 3:20 PM, Kinney, Michael D <michael.d.kinney@intel.com> wrote:
>
> I agree with this proposal.
>
> I also agree with Leif that large patch series
> must be shared on a branch for review.
>
> Mike
>
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org]
>> On Behalf Of Leif Lindholm
>> Sent: Tuesday, November 20, 2018 1:57 AM
>> To: Ni, Ruiyu <ruiyu.ni@intel.com>
>> Cc: edk2-devel@lists.01.org; Gao, Liming
>> <liming.gao@intel.com>; Richardson, Brian
>> <brian.richardson@intel.com>; Cetola, Stephano
>> <stephano.cetola@intel.com>; Kinney, Michael D
>> <michael.d.kinney@intel.com>; Laszlo Ersek
>> <lersek@redhat.com>
>> Subject: Re: [edk2] [RFC] Proposal to remove DuetPkg
>>
>> On Tue, Nov 20, 2018 at 05:27:13AM +0000, Ni, Ruiyu
>> wrote:
>>> All,
>>> DuetPkg depends on Legacy BIOS to provide a UEFI
>> environment. It was
>>> invented in the era when UEFI environment is hard to
>> find. Since now
>>> UEFI is very popular in PC area, we could stop the
>> official support
>>> of this package and remove it from the master.
>>> Anyone who wants to use it still can just grab it from
>> git
>>> history. This is the same as what we did for IPF
>> contents.
>>>
>>> If there is no concern by end of November, we will send
>> out a formal
>>> patch to remove DuetPkg. (Since DuetPkg is big, we will
>> not generate
>>> the huge patch using git command, instead we will just
>> send out the
>>> patch mail with correct title/commit message but empty
>> content.)
>>
>> Works for me. If you could include a link to the patch in
>> a branch
>> where it can be reviewed, that would be ideal.
>>
>> /
>> Leif
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-11-21 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 5:27 [RFC] Proposal to remove DuetPkg Ni, Ruiyu
2018-11-20 8:46 ` Laszlo Ersek
2018-11-20 9:57 ` Leif Lindholm
2018-11-20 23:20 ` Kinney, Michael D
2018-11-20 23:21 ` Kinney, Michael D
2018-11-21 11:01 ` Ni, Ruiyu
2018-11-21 0:59 ` Andrew Fish [this message]
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=4108E983-A970-4530-B8B2-9F0FEEEABCFA@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