From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Intel Microcode
Date: Fri, 24 Aug 2018 11:26:29 +0100 [thread overview]
Message-ID: <f7c0f68dd939ec59c216568cfb89604639ab006f.camel@ipfire.org> (raw)
In-Reply-To: <20180824062548.GA12826@tarvainen.info>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Fri, 2018-08-24 at 09:25 +0300, Tapani Tarvainen wrote:
> On Thu, Aug 23, 2018 at 09:11:20PM +0200, Peter Müller (peter.mueller(a)link38.eu) wrote:
>
> > https://www.heise.de/newsticker/meldung/Aerger-ueber-Intels-Lizenzbedingungen-fuer-Sicherheits-Updates-4144515.html
> >
> > It says there: Intel announces to publish a changed version of the license
> > soon.
>
> They have. Without that obnoxious "no benchmarking" clause.
> I believe the new version is this:
>
> https://01.org/mcu-path-license-2018
Yes, that is the new license. Guess we will have to update the package
again...
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlt/3VUACgkQgHnw/2+Q
CQe4tw//ffXgVY8JiLNIUFa/vEee8yX52jphBH6YSTe57OuOd+Se96o9ndapKr0+
BN6N0HIXfrRspHEnQ9tXWrRZRlHBSeqeWJSsABqctfCFuty1TMqbSL53U7CP7jEd
tOTrbofR9TS3PO/zS+vq2dVZtPX8FFroQtxYjn4Vge2GGNU1y+UGa7gjx+wrkIzq
pbqEuDNiiP7ThYquyOh2OKPW1v5S6oStB5jbfgZRF7AlLCO1ObhspUBURrp9xTHb
tG/tmCaN0btnwVbkLAOCU4V3VHvIc9fguA/id1e5ddnG4g0/rBSjh3Br/mdtuh8Y
n6hRebrjud4pD9DiUFcji06RxwumLUEanDn3ub7Z5lXOkkOK1kO6ZkmiUGR1FdZJ
xO/nlLj4mhblWmxJTKJsCrD1JoWwMOxT8Ti6wHPZPEUDN7StV1A+CkNJun1tTRiW
7JIoZ2DYP4bqevT3HTlBqZHBe/mjx7HqK+l48SjGnY+YHIx/VtbxCZkswZ1Vbyzi
37ORhrSIhDILJXIvXoKHAsdhXbnW2zror51Fd2oyOQCmlqtjVw/VXx850Ca0itmc
XbtbEnNBnPpNMxR1jIVyciCDESx4mArzSbqGNLoeU0GL3Ehnrs4Zz7H4ikKO9WC+
En7VYFir0aMpjBjDuTWF72978UVIWmwwdPjhOO6bXkyQ8ZnxlLE=
=A3sl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-08-24 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7e10425-44bc-4dc9-97f2-3b48641088cd@rymes.com>
2018-08-23 14:38 ` Michael Tremer
2018-08-23 14:49 ` Tom Rymes
2018-08-23 14:50 ` Michael Tremer
2018-08-23 19:11 ` Peter Müller
2018-08-24 6:25 ` Tapani Tarvainen
2018-08-24 10:26 ` Michael Tremer [this message]
2018-08-24 10:39 ` Michael Tremer
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-all 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=f7c0f68dd939ec59c216568cfb89604639ab006f.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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