From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Intel Microcode
Date: Fri, 24 Aug 2018 09:25:48 +0300 [thread overview]
Message-ID: <20180824062548.GA12826@tarvainen.info> (raw)
In-Reply-To: <7ccf12cd-e37e-d5bf-3821-2aca28928122@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
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
--
Tapani Tarvainen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-24 6:25 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 [this message]
2018-08-24 10:26 ` Michael Tremer
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=20180824062548.GA12826@tarvainen.info \
--to=ipfire@tapanitarvainen.fi \
--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