From: dan <dandenson@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] forums?
Date: Tue, 3 Oct 2023 09:36:20 -0600 [thread overview]
Message-ID: <CAA_JP8XoJ8uBLaOD3VAb094wg86ysPZtMYr8db8gpw6EDLoq5g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
mailing lists are fun... but this would be so much better in forums IMO.
We're already leapfrogging conversations because we have a lot of minds
pushing thoughts in...
[-- Attachment #2: Type: text/html, Size: 201 bytes --]
next reply other threads:[~2023-10-03 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 15:36 dan [this message]
2023-10-03 16:33 ` Dennis Burgess
2023-10-03 16:34 ` dan
2023-10-03 20:49 ` Daniel Corbe
2023-10-04 0:41 ` David Lang
2023-10-04 0:57 ` Christopher Hawker
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA_JP8XoJ8uBLaOD3VAb094wg86ysPZtMYr8db8gpw6EDLoq5g@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=nnagain@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