| 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: Mon, 30 Apr 2007 00:48:28 +0200 From: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com> To: "Andi Kleen" <andi@...stfloor.org> Cc: "Thomas Gleixner" <tglx@...utronix.de>, "Adrian Bunk" <bunk@...sta.de>, "Diego Calleja" <diegocg@...il.com>, "Linus Torvalds" <torvalds@...ux-foundation.org>, "Chuck Ebbert" <cebbert@...hat.com>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.21 On 30/04/07, Andi Kleen <andi@...stfloor.org> wrote: > > Right. Simply because these lists are assembled by someone > > > > - who knows how to pick that reports from the mailinglists > > - who knows how to sort them in a useful way > > - who knows how to add the relevant folks on CC > > That all needs to be done by someone initially yes. But then tracking what happens > afterwards is something that can be distributed. A difficult bug can take a long > time to resolve and generate a lot of messages; you don't want to require > the initial sorter to handle all that too. > > It's much more scalable to let the developers update the state themselves > then once they handle the bug. The actual list of known regressions is wiki based. Everyone can update bug status, add references etc. >From time to time, I'll send this list to right people. > > -Andi > Regards, Michal -- Michal K. K. Piotrowski Kernel Monkeys (http://kernel.wikidot.com/start) - 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