From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] ZDNet ruoter review
Date: Fri, 08 Apr 2022 09:59:55 -0700 [thread overview]
Message-ID: <B601D05B61101A2551465AB5@[192.168.69.69]> (raw)
Another router review with no mention of bufferbloat. So I nagged them
about it in the comments.
<https://www.zdnet.com/home-and-office/networking/best-wifi-router/#comment-5821308024>
next reply other threads:[~2022-04-08 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:59 Kenneth Porter [this message]
[not found] <B601D05B61101A2551465AB5@192.168.69.69>
2022-04-08 17:24 ` Dave Taht
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='B601D05B61101A2551465AB5@[192.168.69.69]' \
--to=shiva@sewingwitch.com \
--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