netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
	Linux Advanced Routing & Traffic Control project
	<lartc@lists.linuxsystems.it>
Cc: Andrew Beverley <andy@andybev.com>,
	Andy Furniss <andyqos@ukfsn.org>,
	"John A. Sullivan III" <jsullivan@opensourcedevel.com>,
	Lloyd Standish <lloyd@crnatural.net>
Subject: LARTC mailing list [was: Re: prio + policing filter on ingress?]
Date: Mon, 19 Dec 2011 12:25:10 +0100	[thread overview]
Message-ID: <4EEF1F16.7070306@linuxsystems.it> (raw)
In-Reply-To: <1324288402.15020.7.camel@steve-pc>

Il 19/12/2011 10:53, Andrew Beverley ha scritto:
> On Thu, 2011-12-15 at 20:48 +0000, Andy Furniss wrote:
>> Andrew Beverley wrote:
>>
>>>
>>> Well according to a question just posted to the (new) LARTC mailing
>>> list,
>>
>> Interesting - where's the new list please?
>
> Well, sort of new, it was created recently by Niccolò Belli who wanted
> to restart the LARTC mailing list, so he started his own and added as
> many people from the old list as he could find.
>
> It's had a pretty slow start, but there's been a few questions. Some
> would rather see it hosted at vger (including me), but in all honesty
> there didn't seem to be a huge amount of interest in restarting it at
> all.
>
> http://lists.linuxsystems.it/listinfo/lartc
>
> Andy

I believe there is still some interest, consider there are less than 30 
members in the 'new' lartc mailing list, some of them which probably 
changed their e-mail address.
Anyway I think we should just try to start a new one and see how well it 
goes, considering:
- most people want to keep the actual "LARTC" name
- most people prefer vger, so we should try there first and keep the 
personal server as a backup option
- the content in the LARTC website is under an open license, so we could 
copy-paste it and create a wiki where users can keep it updated. Same 
question here: I can host it without problems but is there a better 
suited alternative?

Cheers,
Niccolò

  reply	other threads:[~2011-12-19 11:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 15:27 prio + policing filter on ingress? Lloyd Standish
2011-12-13 18:25 ` Andrew Beverley
2011-12-13 20:19   ` Lloyd Standish
2011-12-13 21:51     ` Andrew Beverley
2011-12-13 22:53       ` John A. Sullivan III
2011-12-14 20:13         ` Andrew Beverley
2011-12-15 20:48           ` Andy Furniss
2011-12-15 21:29             ` John A. Sullivan III
2011-12-15 22:08               ` Andy Furniss
2011-12-19  9:53             ` Andrew Beverley
2011-12-19 11:25               ` Niccolò Belli [this message]
2011-12-19 17:07                 ` LARTC mailing list [was: Re: prio + policing filter on ingress?] John A. Sullivan III
2011-12-19 17:11                 ` Andrew Beverley
2011-12-19 19:59                   ` LARTC mailing list David Miller
2011-12-19 20:59                     ` Niccolò Belli
2011-12-20 10:45                     ` Andy Furniss

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=4EEF1F16.7070306@linuxsystems.it \
    --to=darkbasic@linuxsystems.it \
    --cc=andy@andybev.com \
    --cc=andyqos@ukfsn.org \
    --cc=jsullivan@opensourcedevel.com \
    --cc=lartc@lists.linuxsystems.it \
    --cc=lloyd@crnatural.net \
    --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).