From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] sqm deployment
Date: Fri, 22 Jun 2018 09:02:47 +0300 [thread overview]
Message-ID: <8B7DDAF8-6416-44CA-ABE5-8F39FDA744B4@gmail.com> (raw)
In-Reply-To: <CAA93jw5MCxtuT6v=GrKS6kQiimaFG8JDYDBwP6kmPs9tp=gXew@mail.gmail.com>
> On 22 Jun, 2018, at 8:32 am, Dave Taht <dave.taht@gmail.com> wrote:
>
>> Question: does anybody know what hides behind eero's sqm name?
>
> It's the sqm-scripts.
So, the likelihood of them adopting Cake is…? :-)
- Jonathan Morton
prev parent reply other threads:[~2018-06-22 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 18:03 [Cerowrt-devel] " Dave Taht
2018-06-15 18:33 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2018-06-15 20:38 ` Sebastian Moeller
2018-06-22 5:32 ` Dave Taht
2018-06-22 6:02 ` Jonathan Morton [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=8B7DDAF8-6416-44CA-ABE5-8F39FDA744B4@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/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