public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"philmd@redhat.com" <philmd@redhat.com>,
	"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [edk2-non-osi] [PATCH 4/6] replace FSP license file.
Date: Mon, 29 Jul 2019 17:50:55 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9D7EC99@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <9764b26c-43c7-7b69-110f-b5dbff0c713e@redhat.com>

This look like a good clean up to remove the PDF file.

Can you please enter a BZ for this.  This patch was already
reviewed in the devel branch, and I prefer to add it in
its current form and look into the conversion from PDF
to a text file as an additional task.

Thanks,

Mike

> -----Original Message-----
> From: devel@edk2.groups.io
> [mailto:devel@edk2.groups.io] On Behalf Of Philippe
> Mathieu-Daudé
> Sent: Monday, July 29, 2019 7:47 AM
> To: devel@edk2.groups.io; Desimone, Nathaniel L
> <nathaniel.l.desimone@intel.com>
> Cc: Yao, Jiewen <jiewen.yao@intel.com>
> Subject: Re: [edk2-devel] [edk2-non-osi] [PATCH 4/6]
> replace FSP license file.
> 
> Hi,
> 
> On 7/25/19 7:35 PM, Nate DeSimone wrote:
> > From: Jiewen Yao <jiewen.yao@intel.com>
> >
> > Contributed-under: TianoCore Contribution Agreement
> 1.0
> > Signed-off-by: Jiewen Yao <jiewen.yao@intel.com>
> > Reviewed-by: Vincent Zimmer
> <vincent.zimmer@intel.com>
> > ---
> >  ... Production RULAC click-through_3-14-18.pdf | Bin
> 487917 -> 0
> > bytes  .../Intel/PurleySiliconBinPkg/FSP_License.pdf
> | Bin 0 -> 15051
> > bytes
> >  2 files changed, 0 insertions(+), 0 deletions(-)
> delete mode 100644
> > Silicon/Intel/PurleySiliconBinPkg/FSP Production
> RULAC
> > click-through_3-14-18.pdf  create mode 100644
> > Silicon/Intel/PurleySiliconBinPkg/FSP_License.pdf
> 
> The exactly same license is available in simple text
> there:
> 
> https://01.org/mcu-path-license-2018
> 
> Is it possible to use it instead of a PDF file?
> 
> > GIT binary patch
> [...]
> 
> 
> 


  reply	other threads:[~2019-07-29 17:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 17:35 [edk2-non-osi] [PATCH 0/6] Merge content from devel-MinPlatform to master Nate DeSimone
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 1/6] Add KabylakeSiliconBinPkg Nate DeSimone
2019-07-26  0:48   ` Chiu, Chasel
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 2/6] Add new Microcode Nate DeSimone
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 3/6] PurleySiliconBinPkg: Initial version Nate DeSimone
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 4/6] replace FSP license file Nate DeSimone
2019-07-29 14:46   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-07-29 17:50     ` Michael D Kinney [this message]
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 5/6] Added TXT ACMs of release 1.7.1 PW Nate DeSimone
2019-07-25 17:35 ` [edk2-non-osi] [PATCH 6/6] Cleanup maintainers, contributions, and licenses Nate DeSimone
2019-07-25 19:51   ` Laszlo Ersek
2019-07-26  0:52   ` Chiu, Chasel
2019-07-26 17:32   ` Leif Lindholm
2019-07-29 20:18     ` [edk2-devel] " Michael D Kinney
2019-07-30 21:34       ` Nate DeSimone
2019-08-01 19:57         ` Michael D Kinney

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=E92EE9817A31E24EB0585FDF735412F5B9D7EC99@ORSMSX113.amr.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