linux-kernel - Re: What can be done to reduce the huge number of build fixes required to release an MM tree?

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]

Message-ID: <14112.1190151354@turing-police.cc.vt.edu>
Date:	Tue, 18 Sep 2007 17:35:54 -0400
From:	Valdis.Kletnieks@...edu
To:	Miles Lane <miles.lane@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: What can be done to reduce the huge number of build fixes required to release an MM tree?

On Tue, 18 Sep 2007 08:23:38 EDT, Miles Lane said:

> and once in while causes trouble?  And 3) Who is causing the most
> cumulative trouble?

Umm... Andrew's Vaio and my Latitude? :)

Seriously though - one big chunk of the problem is almost certainly that Andrew
and I run with .config's and hardware that differ drastically from what the
various maintainers test against, and the rest is that Andrew pulls git trees
that may or may not be ready for prime time.  Not sure if there's any practical
way to "fix" that without adding so much administrivia overhead to render the
whole -mm tree useless as a a preview/early-warning system....

Content of type "application/pgp-signature" skipped