From: Leif Lindholm <leif.lindholm@linaro.org>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Richardson, Brian" <brian.richardson@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"'Andrew Fish (afish@apple.com)'" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: [RFC] Proposal to remove DuetPkg
Date: Tue, 20 Nov 2018 09:57:28 +0000 [thread overview]
Message-ID: <20181120095728.bupflsmqgmpkun5w@bivouac.eciton.net> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5BF0FF83@SHSMSX104.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2018-11-20 9:57 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 [this message]
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
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=20181120095728.bupflsmqgmpkun5w@bivouac.eciton.net \
--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