Stop accept/merge code that does not compile without warnings

Stop accept/merge code that does not compile without warnings

[Fred .]

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.

Re: Stop accept/merge code that does not compile without warnings

[Pekka Enberg]

Hi Fred,

On Sat, Oct 18, 2008 at 4:15 AM, Fred . <eldmannen@gmail.com> wrote:
> 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.

Thanks for the excellent advice! I'm sure we'll all be more careful in
the future knowing you're looking after us.

Keep up the good work.

                   Pekka