mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Valdis.Kletnieks@vt.edu
Cc: Andre Tomt <andre@tomt.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Robert P. J. Day" <rpjday@mindspring.com>
Subject: Re: so ... what *are* candidates for removal?
Date: Wed, 02 May 2007 00:33:50 +0200	[thread overview]
Message-ID: <4637C04E.4070306@s5r6.in-berlin.de> (raw)
In-Reply-To: <10590.1178037443@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Tue, 01 May 2007 17:30:36 +0200, Andre Tomt said:
>> Robert P. J. Day wrote:
> 
>>> http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed
> 
>> Already documented in the kernel tarball, see 
>> Documentation/feature-removal-schedule.txt
> 
> Robert's point is that the file you cited is horrendously out of date, and
> we need to create a consensus of what *should* be in feature-removal-schedule.txt
> so we can update it to correspond to some sort of reality, or at the very least
> some politically correct sanitized view of reality. It currently lists
> stuff scheduled to be removed 18 months ago, and doesn't list stuff that
> everybody agrees deserves to be heaved over the side as soon as the users have
> had "enough warning" (whatever that means)....

It means to get in touch with people who are affected.  Yes, that's the
tough part.

Regarding features that are overdue for removal according to
feature-removal-schedule.txt:

I remember that at least one person used to watch for due dates for
feature removal, wrote the removing patches, and sent them to the
appropriate lists and maintainers.  This either got rid of the obsolete
stuff, or it turned up reasons why some feature could not be removed
just yet and how to update feature-removal-schedule.txt to correctly
reflect that.

So, as they say, Patches Are Welcome.
-- 
Stefan Richter
-=====-=-=== -=-= ---=-
http://arcgraph.de/sr/

  reply	other threads:[~2007-05-01 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 15:01 Robert P. J. Day
2007-05-01 15:30 ` Andre Tomt
2007-05-01 16:37   ` Valdis.Kletnieks
2007-05-01 22:33     ` Stefan Richter [this message]
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=4637C04E.4070306@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=andre@tomt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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®