linux-kernel - Re: [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt

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: <CAM_iQpUHYDT2hnt3h8fF33rp3O9c_VjEftOFUj-qdMdUkxo1tw@mail.gmail.com>
Date:	Thu, 6 Sep 2012 22:29:58 +0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Add feature-removal-schedule.txt removal to feature-removal-schedule.txt

On Tue, Sep 4, 2012 at 11:39 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 2012-08-29 at 09:28 +0800, Cong Wang wrote:
>> On Tue, Aug 28, 2012 at 2:22 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>> > The file feature-removal-schedule.txt is ignored by most people except
>> > for people that add to it. It's more of a global TODO list for
>> > developers than being anything useful by anyone.
>> >
>> > Add a feature removal of removing the feature-removal-schedule.txt.
>> >
>>
>> Hi, Steven,
>>
>> I sometimes remind people to remove features scheduled in this file,
>> by sending a proposed patch. ;)
>
> At Kernel Summit, Linus went on a rant about this file. He said he hates
> it and is totally useless. Basically, it is only used by us developers,
> and is not used by normal users. As it is a dumping ground for all
> developers, this file becomes the biggest conflict during merges that
> Linus does.
>
> There are better ways to tell users something is about to go away. My
> preference is a nasty WARN_ON_ONCE() in the code when the feature is
> used. People tend to report call traces, and you can either tell the
> person, "don't use this" or you know that it is something that is
> actually used and you can't remove it.
>

I don't think feature-removal-schedule.txt is for kernel users, it
is a kind of a TODO list for kernel developers.
--
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/