From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: PortSmash and yesterday's discussion
Date: Tue, 06 Nov 2018 08:57:15 +0000 [thread overview]
Message-ID: <b8d2916662621e72d09e70f75d535c3b23fdf57a.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Hello,
I have written a blog post about the discussion yesterday:
https://blog.ipfire.org/post/more-on-intel-s-hardware-bugs
Let me know if I summed it up correctly what we talked about yesterday and just
for the record if you agree or disagree.
Looking at the topic, I am terribly frustrated but do not have anything
constructive to say...
Best,
-Michael
reply other threads:[~2018-11-06 8:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b8d2916662621e72d09e70f75d535c3b23fdf57a.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