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]

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

Robert P. J. Day wrote:
> On Wed, 2 May 2007, Stefan Richter wrote:
> 
>> 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.
> 
> that's a nice idea, but it doesn't address the problem that someone
> might go to the trouble to create such a patch and send it in, only to
> have that submission generate shrieking along the lines of "OHMIGOD,
> we can't delete that *yet*!!!"

You are absolutely right.

We have to try to avoid this waste of resources when we put features
into feature-removal-schedule.txt.  That's what I meant with "the hard
part" in the other post.

BTW, of course it doesn't suffice to say "we can't remove it yet" after
the due day.  There need to be well-founded reasons for another
deferral.  Of course if there are such reasons, it means something went
wrong when the feature was put into removal schedule.  (Some facts
weren't known.)

> that's the whole point of this wiki page:
> 
> http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed

Yep; if that page helps to collect the facts, then all the better.

Though in the very end, a feature goes away by means of a patch.

[...]
> i'm sure most people here can think of better things to do with their
> time.

Funny (or not so) how this sentence applies to all kinds of activities
into which more than one person is involved.  So let's try to plan our
work carefully and *timely*, to let as little of it go to waste as possible.
-- 
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/