From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: cerowrt related mailing lists created
Date: Thu, 1 Dec 2011 19:35:32 +0100 [thread overview]
Message-ID: <CAA93jw73jCSu4vxHVMakLLqMFsOX4rxm5vFc=vo7g339vT24ug@mail.gmail.com> (raw)
I have created cerowrt-users, cerowrt-devel, and cerowrt-commits
mailing lists on http://lists.bufferbloat.net
Please subscribe to one or more of those if the cerowrt test router subproject
is your interest. I note also you can submit bug reports and comments directly
into the 'cerowrt' user on lists.bufferbloat.net and they will
automagically enter
the bug system there.
For now I plan to keep using the #bufferbloat channel for cerowrt support
unless that gets out of hand too.
I will periodically point out news of import regarding cerowrt and as relating
to bufferbloat to multiple lists here, but let's keep stuff that
mostly cerowrt and
not bloat related over there, ok?
If anyone has any other suggestions for useful lists to create, now is
the time to ask.
One of my thoughts was to resurrect the old lartc list, which
discussed user issues with
traffic shaping and control in particular. It was useful in it's
heyday and there seems
to be some market for the idea re-occurring.
There has been some talk of doing that
instead over on vger.kernel.org, and I'm cool with that, if it happens.
comments?
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
reply other threads:[~2011-12-01 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw73jCSu4vxHVMakLLqMFsOX4rxm5vFc=vo7g339vT24ug@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@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