From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] if you can't tell
Date: Thu, 14 Nov 2013 11:04:31 -0800 [thread overview]
Message-ID: <CAA93jw48vbded_-Pn6de8P6j+=Oz0DgU-Xw5nM30L-a-hHmEPg@mail.gmail.com> (raw)
I am simply horribly, horribly behind on email. I just got back from
canada day before yesterday and am trying to dig out. IETF was both
productive and non-productive in many ways...
was the consensus 3.10.18 was busted worse than 3.10.17? .19 is out
but I'll sink more time into it overall to solve various bugs
(sysupgrade via gui works? but not at the command line?) once and for
all, rather than
keep integrating
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2013-11-14 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 19:04 Dave Taht [this message]
2013-11-14 19:31 ` Sebastian Moeller
2013-11-14 19:36 ` Richard E. Brown
2013-11-14 19:57 ` Dave Taht
2013-11-14 20:11 ` Sebastian Moeller
2013-11-17 21:59 ` Sebastian Moeller
[not found] <52852256.3010401@imap.cc>
2013-11-14 19:20 ` Fred Stratton
2013-11-14 19:21 ` Fred Stratton
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='CAA93jw48vbded_-Pn6de8P6j+=Oz0DgU-Xw5nM30L-a-hHmEPg@mail.gmail.com' \
--to=dave.taht@gmail.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