From: Jonathan Morton <chromatix99@gmail.com>
To: dpreed@deepplum.com
Cc: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] anyone fiddlng with these?
Date: Thu, 15 Feb 2018 15:51:00 +0200 [thread overview]
Message-ID: <CAJq5cE3w5rs2XBFQh66159Ybuaad4Cs7QaC4KpwWyjNJ7Z-FKw@mail.gmail.com> (raw)
In-Reply-To: <1518702402.737522502@mobile.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Hear, hear.
Besides - exactly how is "securely sending messages to the web" useful in
any way? That's the part I've never been able to figure out about the IoT
nonsense.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 269 bytes --]
next prev parent reply other threads:[~2018-02-15 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:46 dpreed
2018-02-15 13:51 ` Jonathan Morton [this message]
2018-02-15 13:52 ` Toke Høiland-Jørgensen
2018-02-15 15:41 ` valdis.kletnieks
2018-02-15 16:03 ` Aaron Wood
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 6:15 Dave Taht
2018-02-14 10:24 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJq5cE3w5rs2XBFQh66159Ybuaad4Cs7QaC4KpwWyjNJ7Z-FKw@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
/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