linux-kernel - Re: feature-removal-schedule.txt updated ??

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] [day] [month] [year] [list]

Date:	Sun, 29 Mar 2009 10:31:44 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Xose Vazquez Perez <xose.vazquez@...il.com>
Cc:	linux-kernel@...r.kernel.org, pavel@...e.cz, mchehab@...radead.org,
	linux@...do.de, hch@....de, arjan@...ux.intel.com,
	kay.sievers@...e.de, rui.zhang@...el.com, len.brown@...el.com,
	htejun@...il.com, jengelh@...putergmbh.de,
	Michael Buesch <mb@...sch.de>, gcosta@...hat.com,
	jirislaby@...il.com, rene.herman@...il.com, ole@....pl,
	tglx@...utronix.de
Subject: Re: feature-removal-schedule.txt updated ??

Hi Xose,

On Sun, 29 Mar 2009 01:57:58 +0100, Xose Vazquez Perez wrote:
> Xose Vazquez Perez wrote:
> 
> > code is still there or file is not updated ?
> > 
> > $ grep ^When  Documentation/feature-removal-schedule.txt | egrep -v "2009|2010|2.6.3[0-9]"
> > When:   2.6.29
> > When:   July 2007
> > When:   December 2008
> > When:   November 2005
> > When:   August 2006
> > When:   before 2.6.19
> > When:   October 2008
> > When:   July 2008
> > When:   August 2007
> > When:   February 2008
> > When: Dec 2008
> > When:   July 2008
> > When:   2.6.27
> > When:   2.6.29
> > When:   After the only user (hal) has seen a release with the patches
> > When: 2.6.29
> 
> today only ONE was fixed!!

This is all not very constructive. For one thing the merge window is
still open, so there are reasonable chances that more entries will be
removed in the next 9 days.

For another, flooding people that way isn't going to fix anything. If
you really want the situation to improve, you have to look at offending
entries individually, contact the responsible person individually, ask
why the entry is still there, and then send a patch removing or
updating it if needs be. This is constructive. Yelling "there are
out-of-date entries in Documentation/feature-removal-schedule.txt" is
not.

In other words, if you are sufficiently bothered by the current
situation and want it to change, then work on it yourself, on your own
time. We aren't your slaves, and we don't owe you anything.

Thanks,
-- 
Jean Delvare
--
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/