mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org, "Adrian Bunk" <bunk@stusta.de>
Subject: Re: {Spam?} Re: {Spam?} [PATCH] NET: Remove obsolete traffic shaper code.
Date: Sun, 15 Apr 2007 14:48:40 +1200	[thread overview]
Message-ID: <5640c7e00704141948n5f82cd8fl64092c720954175f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704141959190.22316@localhost.localdomain>

On 4/15/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> in fact, according to this:
>
> http://lkml.org/lkml/2006/1/13/139
>
> that notice was put in the feature removal file well over a year ago,
> during 2.6.15.  so that would seem to be more than adequate time for
> everyone to prepare for it.  but it must have been deleted from that
> file since then as well.

Yes and that was never merged and so was resent on January 19th, 2006:
http://www.nabble.com/-2.6-patch--schedule-SHAPER-for-removal-t949871.html

At that point people debated about it being too short notice and the
patch never went in.

I therefore think we can't just remove with NO notice.

Ian
-- 
Web: http://wand.net.nz/~iam4/
Blog: http://iansblog.jandi.co.nz
WAND Network Research Group

  reply	other threads:[~2007-04-15  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-14 23:30 Robert P. J. Day
2007-04-14 23:34 ` Rene Herman
2007-04-14 23:38   ` {Spam?} " Robert P. J. Day
2007-04-14 23:55     ` Rene Herman
2007-04-14 23:46 ` Ian McDonald
2007-04-15  0:06   ` {Spam?} " Robert P. J. Day
2007-04-15  2:48     ` Ian McDonald [this message]
2007-04-15 13:37       ` {Spam?} " Robert P. J. Day

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=5640c7e00704141948n5f82cd8fl64092c720954175f@mail.gmail.com \
    --to=ian.mcdonald@jandi.co.nz \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rpjday@mindspring.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

all inboxes | Powered by JetHome®