| 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
| ||
|
Message-ID: <Pine.LNX.4.64.0805291224470.6718@jikos.suse.cz> Date: Thu, 29 May 2008 12:34:19 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> To: Chris Mason <chris.mason@...cle.com> cc: ksummit-2008-discuss@...ts.linux-foundation.org, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project On Wed, 28 May 2008, Chris Mason wrote: > One motivation here is to bring bug reporters from active distro > communities into testing mainline kernels as well. My experience from handling both distro-reported and upstream-reported bugs shows that these two worlds/communitites are really quite different in their nature. Bug reporters who report bug in the vanilla kernel are usually perfectly fine when someone sends them patch to test, they don't have any problem recompiling the patched kernel, testing, and reporting back. This is not the case with distro kernel bug reporters at all. You usually can't just tell them "hey, this patch might fix it, report back if it does". Vast majority of theese users expect the kernel package built for their distro to be provided, so that they can easily install it and test it, but requiring any other effort usually doesn't work. Just my $0.02. -- Jiri Kosina SUSE Labs -- 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