From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: so ... what *are* candidates for removal?
Date: Tue, 1 May 2007 11:01:09 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705011050080.11853@localhost.localdomain> (raw)
at the risk of spawning yet another thread and another flamefest,
what *are* the kernel features that should be considered candidates
for removal, either now or at some point in the future.
please, no discussions about mechanisms or kernel warnings or the
like -- just the features whose value is nearing their end. i'll even
volunteer to collect all that info and summarize it here:
http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed
because that's just the kind of guy i am, and i have the week off, and
i'm bored. :-)
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next reply other threads:[~2007-05-01 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 15:01 Robert P. J. Day [this message]
2007-05-01 15:30 ` Andre Tomt
2007-05-01 16:37 ` Valdis.Kletnieks
2007-05-01 22:33 ` Stefan Richter
2007-05-02 8:28 ` Robert P. J. Day
2007-05-02 9:50 ` Stefan Richter
2007-05-02 10:14 ` John Anthony Kazos Jr.
2007-05-02 10:33 ` Stefan Richter
2007-05-02 10:58 ` Robert P. J. Day
2007-05-02 11:52 ` Neil Brown
2007-05-02 12:31 ` Robert P. J. Day
2007-05-02 13:13 ` Stefan Richter
2007-05-01 17:18 ` Jan Engelhardt
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=Pine.LNX.4.64.0705011050080.11853@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®