archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <>
To: Steven Rostedt <>
	Linus Torvalds <>,
	Andrew Morton <>
Subject: Re: [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt
Date: Thu, 6 Sep 2012 22:29:58 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1346773188.27919.13.camel@gandalf.local.home>

On Tue, Sep 4, 2012 at 11:39 PM, Steven Rostedt <> wrote:
> On Wed, 2012-08-29 at 09:28 +0800, Cong Wang wrote:
>> On Tue, Aug 28, 2012 at 2:22 AM, Steven Rostedt <> wrote:
>> > The file feature-removal-schedule.txt is ignored by most people except
>> > for people that add to it. It's more of a global TODO list for
>> > developers than being anything useful by anyone.
>> >
>> > Add a feature removal of removing the feature-removal-schedule.txt.
>> >
>> Hi, Steven,
>> I sometimes remind people to remove features scheduled in this file,
>> by sending a proposed patch. ;)
> At Kernel Summit, Linus went on a rant about this file. He said he hates
> it and is totally useless. Basically, it is only used by us developers,
> and is not used by normal users. As it is a dumping ground for all
> developers, this file becomes the biggest conflict during merges that
> Linus does.
> There are better ways to tell users something is about to go away. My
> preference is a nasty WARN_ON_ONCE() in the code when the feature is
> used. People tend to report call traces, and you can either tell the
> person, "don't use this" or you know that it is something that is
> actually used and you can't remove it.

I don't think feature-removal-schedule.txt is for kernel users, it
is a kind of a TODO list for kernel developers.

  reply	other threads:[~2012-09-06 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 18:22 [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt Steven Rostedt
2012-08-29  1:28 ` Cong Wang
2012-09-04 15:39   ` Steven Rostedt
2012-09-06 14:29     ` Cong Wang [this message]
2012-09-06 14:42       ` Steven Rostedt
2012-09-06 15:42         ` Randy Dunlap

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).