| 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
| ||
|
Date: Tue, 18 Sep 2007 08:23:38 -0400
From: "Miles Lane" <miles.lane@...il.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: What can be done to reduce the huge number of build fixes required to release an MM tree?
Hello Andrew and all,
What can be done to reduce the huge number of build fixes required to
release an MM tree?
Perhaps it would be helpful if you identified specific individuals who
send you patches that break the build. If necessary, we could keep a
running total. The main thought is that maybe we need to identify who
regularly sends troublesome patches. There are three metrics that
might be good to know: 1) Who sends patches that are regularly
broken, but sends patches rarely? 2) Who sends patches all the time,
and once in while causes trouble? And 3) Who is causing the most
cumulative trouble?
Is there any possibility that we ought to refuse patches from people
who break the build too often?
Another area that might be helpful might be how the patches break
things. Are there major groupings of errors that developers could be
educated about?
I am sorry you are having to work so hard to do your job, Andrew.
Miles
-
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/
Powered by blists - more mailing lists