From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt
Date: Mon, 27 Aug 2012 14:22:05 -0400 [thread overview]
Message-ID: <1346091725.19381.10.camel@pippen.local.home> (raw)
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.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
Documentation/feature-removal-schedule.txt | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index afaff31..dcbb573 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -6,6 +6,17 @@ be removed from this file. The suggested deprecation period is 3 releases.
---------------------------
+What: Documentation/feature-removal-schedule.txt
+When: v3.8
+Why: Developers add their TODO list here, and no one else reads it.
+ It causes a lot of silly conflicts that annoy Linus.
+ There are better ways to remove features than adding your crap here.
+ Add a printk() or 'CONFIG_FOO default n' and see who complains.
+ This file has been proven to be absolutely useless.
+Who: Steven Rostedt <rostedt@goodmis.org>
+
+---------------------------
+
What: ddebug_query="query" boot cmdline param
When: v3.8
Why: obsoleted by dyndbg="query" and module.dyndbg="query"
next reply other threads:[~2012-08-27 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 18:22 Steven Rostedt [this message]
2012-08-29 1:28 ` [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt Cong Wang
2012-09-04 15:39 ` Steven Rostedt
2012-09-06 14:29 ` Cong Wang
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:
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=1346091725.19381.10.camel@pippen.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).