linux-kernel - Re: so ... what *are* candidates for removal?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 02 May 2007 00:33:50 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Valdis.Kletnieks@...edu
CC:	Andre Tomt <andre@...t.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: so ... what *are* candidates for removal?

Valdis.Kletnieks@...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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/