From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Fred ." <eldmannen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stop accept/merge code that does not compile without warnings
Date: Sat, 18 Oct 2008 12:54:39 +0300 [thread overview]
Message-ID: <84144f020810180254u6fa1c3b9t987f06ccd204a81a@mail.gmail.com> (raw)
In-Reply-To: <f188924b0810171815rf486248s9ad1e3f968f907a1@mail.gmail.com>
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
prev parent reply other threads:[~2008-10-18 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 1:15 Fred .
2008-10-18 9:54 ` Pekka Enberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84144f020810180254u6fa1c3b9t987f06ccd204a81a@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=eldmannen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®