From: Mike Wright <nobody@nospam.hostisimo.com>
To: Lewis Rosenthal <lgrosenthal@2rosenthals.com>,
Linux Advanced Routing & Traffic Control mailing list
<lartc@vger.kernel.org>
Subject: Re: Status of the LARTC project and of this list
Date: Tue, 31 Oct 2023 17:16:32 -0700 [thread overview]
Message-ID: <d94aab58-416c-48d9-8fd7-05ec041a9bf4@nospam.hostisimo.com> (raw)
In-Reply-To: <7933E6AF-7337-4AA9-A9F9-736196A11BC8@2rosenthals.com>
On 10/31/23 15:46, Lewis Rosenthal wrote:
> The overarching point, from my perspective, is that this list is not a "project" at all, but a clearinghouse for configuration of routing & traffic control on the platform.
>
> As such, sunsetting it would be counterproductive.
>
> Anyway, that's the view from this tiny (and very quiet) corner, rudely top-posted (sorry about that).
I'd like to second Lewis' comment. I've received help there that I
couldn't have found elsewhere.
Every time I've poked around for things like traffic control, routing,
and firewalls the most arcane information invariably points here.
That said, I don't know how many of the advanced routing members still
haunt the list. Every now and then Grant Taylor shows up and he has a
*wealth* of knowledge from the wayback to current.
WRT low traffic: rarely used doesn't mean unused.
next prev parent reply other threads:[~2023-11-01 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:57 Status of the LARTC project and of this list Konstantin Ryabitsev
2023-10-31 20:53 ` Rich Brown
2023-10-31 22:46 ` Lewis Rosenthal
2023-11-01 0:16 ` Mike Wright [this message]
2023-11-01 2:26 ` Grant Taylor
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=d94aab58-416c-48d9-8fd7-05ec041a9bf4@nospam.hostisimo.com \
--to=nobody@nospam.hostisimo.com \
--cc=lartc@vger.kernel.org \
--cc=lgrosenthal@2rosenthals.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).