From: "Dandan Bi" <dandan.bi@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Carsey, Jaben" <jaben.carsey@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [patch] ShellBinPkg: Remove ShellBinPkg
Date: Thu, 18 Apr 2019 01:11:41 +0000 [thread overview]
Message-ID: <3C0D5C461C9E904E8F62152F6274C0BB40BBD0CA@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <72474caf-c936-1ff7-a92c-b0f279d5418e@redhat.com>
Thank you all.
I will update the patch according to Laszlo's comments before commit the patch.
Thanks,
Dandan
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, April 17, 2019 6:53 PM
> To: Ard Biesheuvel <ard.biesheuvel@linaro.org>; Bi, Dandan
> <dandan.bi@intel.com>
> Cc: edk2-devel-groups-io <devel@edk2.groups.io>; Carsey, Jaben
> <jaben.carsey@intel.com>; Ni, Ray <ray.ni@intel.com>; Leif Lindholm
> <leif.lindholm@linaro.org>; Gao, Liming <liming.gao@intel.com>
> Subject: Re: [patch] ShellBinPkg: Remove ShellBinPkg
>
> On 04/17/19 09:16, Ard Biesheuvel wrote:
> > On Tue, 16 Apr 2019 at 23:40, Dandan Bi <dandan.bi@intel.com> wrote:
> >>
> >> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1675
> >>
> >> Remove ShellBinPkg from edk2.
> >> If developers work on current edk2 master and still want to use Shell
> >> binary after this removal, they can get it from source code in the
> >> Assets part of edk2-stable201903 tag release page.
> >> And from next release (edk2-stable201905 tag), we will publish all
> >> Shell binaries to the according Assets part directly.
> >> edk2 release link: https://github.com/tianocore/edk2/releases
> >>
> >> Cc: Jaben Carsey <jaben.carsey@intel.com>
> >> Cc: Ray Ni <ray.ni@intel.com>
> >> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> >> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >> Cc: Liming Gao <liming.gao@intel.com>
> >> Cc: Laszlo Ersek <lersek@redhat.com>
> >> Signed-off-by: Dandan Bi <dandan.bi@intel.com>
> >
> > Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > BTW you can use the --no-binary option to git to omit the binary diffs
> > in the patch. Especially when deleting binaries, that saves a lot of
> > hassle dealing with a multimegabyte patch email.
>
> +1
>
> For the patch, I have a request towards Dandan: regarding the line
>
> +Maintainers for stable Shell binaries generation when need to publish Shell
> binaries with edk2 release:
>
> please:
>
> (1) wrap it with an 80-char margin,
> (2) please insert a blank line just above it.
>
> With those:
>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
>
> Thanks
> Laszlo
next prev parent reply other threads:[~2019-04-18 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 6:40 [patch] ShellBinPkg: Remove ShellBinPkg Dandan Bi
2019-04-17 7:16 ` Ard Biesheuvel
2019-04-17 10:52 ` Laszlo Ersek
2019-04-18 1:11 ` Dandan Bi [this message]
2019-04-23 1:58 ` Liming Gao
2019-04-23 2:03 ` Carsey, Jaben
2019-05-08 6:34 ` [edk2-devel] " MinnowWare
2019-05-08 6:45 ` Liming Gao
2019-05-08 17:29 ` Michael D Kinney
2019-05-09 13:25 ` Minnow Ware
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=3C0D5C461C9E904E8F62152F6274C0BB40BBD0CA@SHSMSX104.ccr.corp.intel.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