From: dpreed@reed.com
To: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] SInce I mentioned this crew's work in a post, I don't want anyone to be surprised.
Date: Tue, 6 Jan 2015 12:26:17 -0500 (EST) [thread overview]
Message-ID: <1420565177.062826426@apps.rackspace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 113 bytes --]
[ GoGo does not need to run “Man in the Middle Attacks” on YouTube ]( http://www.reed.com/blog-dpr/?p=174 )
[-- Attachment #2: Type: text/html, Size: 315 bytes --]
next reply other threads:[~2015-01-06 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 17:26 dpreed [this message]
2015-01-06 19:37 ` Dave Taht
2015-01-06 19:43 ` David Lang
2015-01-06 19:50 ` Jim Gettys
2015-01-19 19:17 ` Aaron Wood
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=1420565177.062826426@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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