From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Documentation/feature-removal-schedule.txt to be updated soon?
Date: Sun, 3 Jan 2010 06:54:10 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001030652110.6587@localhost> (raw)
as is my wont, i will mutter quietly about the amount of content in
the file Documentation/feature-removal-schedule.txt referring to stuff
that should have been removed ages ago (some of it is dated as far
back as 2005).
is there any plan on bringing that file up to date, and/or deleting
stuff that's been marked for deletion for years?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2010-01-03 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 11:54 Robert P. J. Day [this message]
2010-01-03 21:29 ` Documentation/feature-removal-schedule.txt to be updated soon? Greg KH
2010-01-08 10:23 ` Robert P. J. Day
2010-01-08 15:46 ` Stefan Richter
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=alpine.LFD.2.00.1001030652110.6587@localhost \
--to=rpjday@crashcourse.ca \
--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