linux-kernel - Re: How to remove 2000+ lines from 400+ defconfig files?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1321384889.20271.217.camel@x61.thuisdomein>
Date:	Tue, 15 Nov 2011 20:21:29 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Dave Jones <davej@...hat.com>
Cc:	Michal Marek <mmarek@...e.cz>, Jiri Kosina <jkosina@...e.cz>,
	linux-kernel@...r.kernel.org
Subject: Re: How to remove 2000+ lines from 400+ defconfig files?

On Tue, 2011-11-15 at 13:57 -0500, Dave Jones wrote:
> It seems to me that these files have always been very neglected.

Almost all of them (ie, 426 of 437) had one or more outdated macros (ie,
mentioned a macro that I could not link to a current Kconfig symbol).

With some, or perhaps a lot of, effort we might learn how long they've
been neglected. For that we need to know when every one of those 161
Kconfig symbols got dropped and see what the oldest Kconfig symbol
(turned into a macro) is in each of those 426 Kconfig files. But I'm not
sure if that actually would tell us much. I guess it's easier to just
conclude that, yes, they are rather neglected.

Paul Bolle

--
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/