Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Nyt missed bloat on airplane WiFi entirely
Date: Sat, 24 Jan 2015 10:00:49 -0500 (EST)	[thread overview]
Message-ID: <1422111649.634227272@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6oui+odvJ3+6xQFz93x-udQ=KZMdZT1Lw2Ubaf9VLo2g@mail.gmail.com>

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


Yeah.  Someone should send them to my blog post.


On Thursday, January 22, 2015 11:16pm, "Dave Taht" <dave.taht@gmail.com> said:



[ http://mobile.nytimes.com/2015/01/22/style/the-sorry-state-of-in-flight-wi-fi.html?_r=2&referrer= ]( http://mobile.nytimes.com/2015/01/22/style/the-sorry-state-of-in-flight-wi-fi.html?_r=2&referrer= )

[-- Attachment #2: Type: text/html, Size: 820 bytes --]

      reply	other threads:[~2015-01-24 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  4:16 Dave Taht
2015-01-24 15:00 ` dpreed [this message]

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=1422111649.634227272@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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