Re: [RFC] Proposal to remove DuetPkg

["Kinney, Michael D" <michael.d.kinney@intel.com>]

Ray,

One additional note.  There are some tools in
BaseTools that are only used by Duet.  We should
remove those tools too.

Mike

> -----Original Message-----
> From: Kinney, Michael D
> Sent: Tuesday, November 20, 2018 3:21 PM
> To: Leif Lindholm <leif.lindholm@linaro.org>; Ni, Ruiyu
> <ruiyu.ni@intel.com>; Kinney, Michael D
> <michael.d.kinney@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>; Laszlo Ersek
> <lersek@redhat.com>
> Subject: RE: [edk2] [RFC] Proposal to remove DuetPkg
> 
> 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