linux-kernel - Stop accept/merge code that does not compile without warnings

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-next>] [day] [month] [year] [list]

Message-ID: <f188924b0810171815rf486248s9ad1e3f968f907a1@mail.gmail.com>
Date:	Sat, 18 Oct 2008 03:15:37 +0200
From:	"Fred ." <eldmannen@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Stop accept/merge code that does not compile without warnings

I read that Linus merged the GEM code.
He said about it that it was untested crap code that didn't compile
cleanly, it spitted out compiler warnings, and the code was ugly,
buggy and bad.

Kernel development is supposed to be done by professionals.
Please stop merge code that does not compile without warnings.
If when you compile it, if it does spit out warnings, then reject it!

We need professional quality, we cant merge any crap, else we get
unstable kernel with lots of bugs.
Kernel developers are supposed to be expert programmers, they
shouldn't have code that spits out warnings.
--
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/