All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Advanced Routing & Traffic Control project
	<lartc@lists.linuxsystems.it>,
	linux-new-lists@vger.kernel.org, netfilter@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [LARTC] LARTC mailing list
Date: Sun, 13 Nov 2011 21:42:01 +0000	[thread overview]
Message-ID: <1321220521.1965.13.camel@andybev-desktop> (raw)
In-Reply-To: <alpine.LNX.2.01.1111021641440.17999@frira.zrqbmnf.qr>

On Wed, 2011-11-02 at 16:43 +0100, Jan Engelhardt wrote:
> On Saturday 2011-10-22 16:10, Andrew Beverley wrote:
> 
> >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?
> 
> Might as well just go to netfilter for now, it's not like as if the 
> traffic was as much as linux-kernel.

Yep, may as well, they seem to be posted there anyway. I was just
conscious that there doesn't appear to be many "tc" experts, because
those sort of questions don't get much of a response.

I'd love to spend some time on some tc documentation one day...

Andy


--
To unsubscribe from this list: send the line "unsubscribe linux-new-lists" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Beverley <andy@andybev.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Advanced Routing & Traffic Control project
	<lartc@lists.linuxsystems.it>,
	linux-new-lists@vger.kernel.org, netfilter@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [LARTC] LARTC mailing list
Date: Sun, 13 Nov 2011 21:42:01 +0000	[thread overview]
Message-ID: <1321220521.1965.13.camel@andybev-desktop> (raw)
In-Reply-To: <alpine.LNX.2.01.1111021641440.17999@frira.zrqbmnf.qr>

On Wed, 2011-11-02 at 16:43 +0100, Jan Engelhardt wrote:
> On Saturday 2011-10-22 16:10, Andrew Beverley wrote:
> 
> >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?
> 
> Might as well just go to netfilter for now, it's not like as if the 
> traffic was as much as linux-kernel.

Yep, may as well, they seem to be posted there anyway. I was just
conscious that there doesn't appear to be many "tc" experts, because
those sort of questions don't get much of a response.

I'd love to spend some time on some tc documentation one day...

Andy


--
To unsubscribe from this list: send the line "unsubscribe linux-new-lists" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-11-13 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EA2BF3D.1010107@linuxsystems.it>
2011-10-22 14:10 ` [LARTC] LARTC mailing list Andrew Beverley
2011-10-22 14:10   ` Andrew Beverley
2011-11-02 15:43   ` Jan Engelhardt
2011-11-02 15:43     ` Jan Engelhardt
2011-11-13 21:42     ` Andrew Beverley [this message]
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-13 21:39       ` Andrew Beverley
2011-11-14  0:44       ` Ben Hutchings
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=1321220521.1965.13.camel@andybev-desktop \
    --to=andy@andybev.com \
    --cc=jengelh@medozas.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.