From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: feature-removal-schedule.txt is getting out of date again
Date: Wed, 6 Feb 2008 04:20:40 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802060419140.17178@localhost.localdomain> (raw)
yes, i realize i'm sounding like a broken record but, once again,
Documentation/feature-removal-schedule.txt is slipping out of date WRT
items that are now slightly, if not noticeably, behind schedule for
removal.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca
Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
next reply other threads:[~2008-02-06 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 9:20 Robert P. J. Day [this message]
2008-02-06 19:54 ` feature-removal-schedule.txt is getting out of date again Bartlomiej Zolnierkiewicz
2008-02-06 19:49 ` Harvey Harrison
2008-02-06 20:07 ` Bartlomiej Zolnierkiewicz
2008-02-07 10:35 ` Robert P. J. Day
2008-02-06 19:56 ` Harvey Harrison
2008-02-07 17:31 ` Robert P. J. Day
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.1.00.0802060419140.17178@localhost.localdomain \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.