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, 2 May 2007 06:14:32 -0400 (EDT)
From:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	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?

> >> 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.)

So when this sort of thing comes up, why can't somebody put together a 
trivial patch to update feature-removal-schedule.txt? If a deadline is 
reached, and a removal is attempted and aborted, the deadline should be 
extended, obviously. So then the patches can be resubmitted (or recreated, 
even) when the new deadline is reached, da capo.
-
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/