public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: Intel Microcode
Date: Thu, 23 Aug 2018 10:49:02 -0400	[thread overview]
Message-ID: <c7cb5bd7-aa7d-c8b5-ef96-b39a7c796f04@rymes.com> (raw)
In-Reply-To: <c901227803752aaf18f9c673950044f872a786be.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On 08/23/2018 10:38 AM, Michael Tremer wrote:
> On Thu, 2018-08-23 at 10:26 -0400, Tom Rymes wrote:
>> On 08/23/2018 9:34 AM, Michael Tremer wrote:
>>> On Wed, 2018-08-22 at 19:36 +0200, Peter Müller wrote:

[snip]

>> I see the desire to err on the side of caution, plus the desire to put
>> pressure on Intel to modify the license, but I'd argue it's overkill.
> 
> It is just ridiculous from my angle. Their primary sales argument is to
> be on top of the list of each benchmark out there. They probably forgot
> about that.
> 
> But this is more about a slight change to hide that they messed up
> *massively* here and a very bad attempt to cover it up. Now they got a
> proper Streisand going. Well done Intel.

[snip]

I'm all for holding off on this as a principle thing, as it's clear that 
Intel's lawyers are trying to pull a fast one. From a practical 
standpoint, though, it's probably less of a problem.

Tom

  reply	other threads:[~2018-08-23 14:49 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 [this message]
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
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=c7cb5bd7-aa7d-c8b5-ef96-b39a7c796f04@rymes.com \
    --to=trymes@rymes.com \
    --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