From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Ni, Ray" <ray.ni@intel.com>, "Bi, Dandan" <dandan.bi@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Cetola, Stephano" <stephano.cetola@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: [RFC] Plan to delete ShellBinPkg from edk2/master
Date: Wed, 3 Apr 2019 18:07:04 +0200 [thread overview]
Message-ID: <565232dc-a0ff-7b1b-3a7c-9c6db0b26969@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9C774C3@ORSMSX112.amr.corp.intel.com>
On 04/03/19 17:49, Kinney, Michael D wrote:
> Laszlo,
>
> I think it makes sense to post validated shell binaries
> with the edk2-stable tag releases. GitHub does support
> this when a release tag is made.
>
> However, we would need to make it simple for a platform
> to use a binary from that location. We may need some
> enhancements to pull in binary artifacts from different
> locations to support a platform build that uses one or
> more pre-built binaries.
Can PREBUILD scripts (written by platform owners) download the required
binaries?
Thanks,
Laszlo
next prev parent reply other threads:[~2019-04-03 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 5:38 [RFC] Plan to delete ShellBinPkg from edk2/master Bi, Dandan
2019-04-02 8:49 ` Laszlo Ersek
2019-04-02 9:12 ` Leif Lindholm
2019-04-02 11:29 ` Ryszard Knop
2019-04-02 11:45 ` Laszlo Ersek
2019-04-02 11:50 ` Ryszard Knop
2019-04-02 12:56 ` Laszlo Ersek
2019-04-03 2:17 ` Ni, Ray
2019-04-03 10:09 ` Laszlo Ersek
2019-04-03 15:49 ` Kinney, Michael D
2019-04-03 16:07 ` Laszlo Ersek [this message]
2019-04-03 21:47 ` [edk2] " Michael D Kinney
2019-04-04 3:42 ` ray.ni
2019-04-04 4:09 ` [edk2-devel] " Andrew Fish
2019-04-04 10:45 ` Laszlo Ersek
2019-04-04 15:10 ` Andrew Fish
2019-04-04 16:06 ` Laszlo Ersek
2019-04-04 16:36 ` Andrew Fish
2019-04-08 8:08 ` Dandan Bi
2019-04-15 14:58 ` Liming Gao
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=565232dc-a0ff-7b1b-3a7c-9c6db0b26969@redhat.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