From: Dave Taht <dave@taht.net>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] bufferbloat.net updated
Date: Thu, 23 Jan 2020 17:06:04 -0800 [thread overview]
Message-ID: <87sgk5acjn.fsf@taht.net> (raw)
In-Reply-To: <EDE1C237-BFD4-40AD-8184-75144FB41189@gmail.com> (Rich Brown's message of "Thu, 23 Jan 2020 16:30:23 -0500")
thank you very much for the updates!
I'd rather like to improve upon the
https://www.bufferbloat.net/projects/codel/wiki/ link one day...
Rich Brown <richb.hanover@gmail.com> writes:
> Folks,
>
> I updated a bunch of pages on bufferbloat.net that I often refer to:
>
> - Main Bloat page - Added a TL;DR with links for measuring and fixing bufferbloat above the Detailed Info
> https://www.bufferbloat.net/projects/bloat/wiki/
>
> - What Can I Do About Bufferbloat? I simplified the page to actually describe what people can do...
> https://www.bufferbloat.net/projects/bloat/wiki/What_can_I_do_about_Bufferbloat/
>
> - Getting SQM Right - I improved the description of RRUL charts, and indicated that the tuning session is still relevant
> https://www.bufferbloat.net/projects/bloat/wiki/Getting_SQM_Running_Right/
>
> - Throughout the site:
> - Note that CeroWrt became OpenWrt
> - Note that LEDE became OpenWrt
> - Fixed menu structure on the right to list OpenWrt (not LEDE) and CeroWrt (link to its archive of articles)
>
> - Assorted minor changes and link fixes.
>
> You're free to make continued edits - I'm content with the site for now. Thanks.
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2020-01-24 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 21:30 Rich Brown
2020-01-24 1:06 ` Dave Taht [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgk5acjn.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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