linux-kernel - Re: so what *is* obsolete and removable?

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: <4624E1DE.2040300@imap.cc>
Date:	Tue, 17 Apr 2007 17:03:58 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Tilman Schmidt <tilman@...p.cc>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	"Robert P. J. Day" <rpjday@...dspring.com>,
	i4ldeveloper@...tserv.isdn4linux.de, Karsten Keil <kkeil@...e.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: so what *is* obsolete and removable?

On Tue, 17 Apr 2007 14:40:54 +0100, Alan Cox wrote:
> If the obsolete tag is to be removed then it needs a formal maintainer,
> all the obsolete interface usage cleaning up and the like otherwise at
> some point in a clean up it is going to end up breaking and migrating to
> && BROKEN as well.

I'm not sure I understand. What do you mean by "obsolete interface
usage"? What sort of cleaning up needs to be done? What sort of
breakage do you anticipate in the event of a clean up?

Thanks
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)