[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1346773188.27919.13.camel@gandalf.local.home>
Date: Tue, 04 Sep 2012 11:39:48 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Add feature-removal-schedule.txt removal to
feature-removal-schedule.txt
On Wed, 2012-08-29 at 09:28 +0800, Cong Wang wrote:
> On Tue, Aug 28, 2012 at 2:22 AM, Steven Rostedt <rostedt@...dmis.org> 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.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists