| 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: <200903241918.29929.sinter.salt@gmx.de> Date: Tue, 24 Mar 2009 19:18:29 +0100 From: sinter <sinter.salt@....de> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: linux-kernel@...r.kernel.org Subject: Re: BUG in 2.6.29 final: broken network connection Am Dienstag 24 März 2009 18:25:03 schrieben Sie: > > It cost me almost 1 complete day > > Wouldn't it have been simpler to wait when you found a problem and read > Ingo's email on the subject from a few hours ago ? Wouldn't it be simpler to restrictively avoid crap code in final kernel versions? And if that does not work by appeal shouldn't the netdev maintainer simply be substituted? Who needs a maintainer adding his SOB with closed eyes under untested crap code? Who needs someone like that for kernel development? -- 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