From: Andrew Beverley <andy@andybev.com>
To: Linux Advanced Routing & Traffic Control project
<lartc@lists.linuxsystems.it>
Cc: linux-new-lists@vger.kernel.org, netfilter@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [LARTC] LARTC mailing list
Date: Sat, 22 Oct 2011 15:10:34 +0100 [thread overview]
Message-ID: <1319292634.26402.6302.camel@andybev-desktop> (raw)
In-Reply-To: <4EA2BF3D.1010107@linuxsystems.it>
On Sat, 2011-10-22 at 15:03 +0200, Niccolò Belli wrote:
> Is someone still interested to bring LARTC to a new life?
> I'm sorry for the subscription but the list didn't work anymore and it
> was unfeasible to CC 30+ addresses. Let me know if you want to
> unsubscribe and you don't know how to.
Thanks for doing this Niccolo. However, I'd rather see it hosted at
vger.kernel.org for all the reasons previously outlined.
I was actually going to suggest a new list called net-users instead.
There is netdev, netfilter-devel and netfilter, but not a general
networking users list.
User questions do get asked on netdev, and some non-netfilter questions
get asked on the netfilter list, but it would seem sensible to have a
general networking users list that would include LARTC questions.
Comments anyone?
Andy
next parent reply other threads:[~2011-10-22 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EA2BF3D.1010107@linuxsystems.it>
2011-10-22 14:10 ` Andrew Beverley [this message]
2011-11-02 15:43 ` [LARTC] LARTC mailing list Jan Engelhardt
2011-11-13 21:42 ` Andrew Beverley
2011-11-13 21:56 ` Dave Taht
2011-11-13 22:02 ` Niccolò Belli
2011-11-14 4:30 ` Jan Engelhardt
[not found] ` <CAAQ01U7iwOMD9xrq3y_dOwvbmHRJZFU6VDb6QxW3qDa8mZWQnQ@mail.gmail.com>
2011-11-14 11:24 ` Niccolò Belli
2011-11-02 17:54 ` Benjamin Poirier
2011-11-13 21:39 ` Andrew Beverley
2011-11-14 0:44 ` Ben Hutchings
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=1319292634.26402.6302.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=lartc@lists.linuxsystems.it \
--cc=linux-new-lists@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
/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 NNTP newsgroup(s).