From: j.neuschaefer@gmx.net (Jonathan Neuschäfer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: feature removal schedule is removed ?
Date: Mon, 25 Mar 2013 14:22:04 +0100 [thread overview]
Message-ID: <20130325132200.GA3246@debian.debian> (raw)
In-Reply-To: <CAJJAcoeOi5XW8mBxvxx=o67nyiEUuZoxSE8hAQ=t=rYS+9vMrg@mail.gmail.com>
On Mon, Mar 25, 2013 at 10:15:22AM +0200, David Shwatrz wrote:
> Hi,
> Once upon a time there was a feature removal schedule in Documentation:
> http://lxr.free-electrons.com/source/Documentation/feature-removal-schedule.txt?v=3.6
>
> Was it removed ? I cannot find it in recent kernels (like 3.9.0-rc4)
Yes.
$ git show --summary 9c0ece069b3
commit 9c0ece069b32e8e122aea71aa47181c10eb85ba7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon Oct 1 15:21:43 2012 -0700
Get rid of Documentation/feature-removal.txt
This file has turned out to be a pure write-only file that causes merge
conflicts and has no actual redeeming features.
There is never any reason to add stuff to this idiotic file. Either
something isn't getting used, and you should just remove it, or there is
no excuse for removing it in the first place. Just stop the idiocy.
It has also been the excuse for just plain bad behavior ("Hey, I don't
like xyz, so let's mark it for removal" followed by "Hey, look, it been
in feature-removal.txt for six months now, so we should remove it").
The recent bogus setitimer() ABI change request was just the most recent
example of pointless and incorrect mental masturbation involving this
file, and I'm tired of the silly and pointless conflicts in the file.
This removal was discussed during the recent kernel summit, and while
Steven Rostedt suggested we should just enter the file itself in the
feature-removal schedule (to see if anybody who edits the file actually
looks at it), that's cute but non-productive.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
delete mode 100644 Documentation/feature-removal-schedule.txt
$ git describe --contains 9c0ece06
v3.7-rc1~165
Greetings,
Jonathan Neusch?fer
prev parent reply other threads:[~2013-03-25 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 8:15 feature removal schedule is removed ? David Shwatrz
2013-03-25 13:13 ` Tobias Boege
2013-03-25 13:22 ` Jonathan Neuschäfer [this message]
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=20130325132200.GA3246@debian.debian \
--to=j.neuschaefer@gmx.net \
--cc=kernelnewbies@lists.kernelnewbies.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).