From: Adrian Bunk <bunk@stusta.de>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] schedule SHAPER for removal
Date: Sat, 21 Jan 2006 01:48:48 +0100 [thread overview]
Message-ID: <20060121004848.GM31803@stusta.de> (raw)
In-Reply-To: <20060119215722.GO16285@kvack.org>
On Thu, Jan 19, 2006 at 04:57:22PM -0500, Benjamin LaHaise wrote:
> On Thu, Jan 19, 2006 at 03:11:50AM +0100, Adrian Bunk wrote:
> > +What: Traffic Shaper (CONFIG_SHAPER)
> > +When: July 2006
> > +Why: obsoleted by the code in net/sched/
> > +Who: Adrian Bunk <bunk@stusta.de
>
> This length of obsolete cycles is way too short -- it's not even enough
> time for a single release of a distro to ship with the feature marked as
> obsolete.
Do we really have to wait the three years between stable Debian releases
for removing an obsolete driver that has always been marked as
EXPERIMENTAL?
Please be serious.
> -ben
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-21 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 2:11 [2.6 patch] schedule SHAPER for removal Adrian Bunk
2006-01-19 20:18 ` Jan Engelhardt
2006-01-19 21:57 ` Benjamin LaHaise
2006-01-21 0:48 ` Adrian Bunk [this message]
2006-01-22 17:47 ` Benjamin LaHaise
2006-01-22 18:20 ` Adrian Bunk
2006-01-22 18:32 ` Arjan van de Ven
2006-01-22 21:21 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-01-11 0:37 [2.6 patch] drivers/net/{,wireless/}Kconfig: remove dead URL Adrian Bunk
2006-01-11 0:46 ` David Woodhouse
2006-01-11 0:53 ` Andi Kleen
2006-01-11 1:58 ` Alan Cox
2006-01-13 14:13 ` [2.6 patch] schedule SHAPER for removal Adrian Bunk
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=20060121004848.GM31803@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.