From: Pekka Enberg <penberg@gmail.com>
To: "David N. Welton" <davidw@dedasys.com>
Cc: dsd@gentoo.org, linux-kernel@vger.kernel.org
Subject: Re: rootdelay
Date: Wed, 27 Apr 2005 11:01:28 +0300 [thread overview]
Message-ID: <84144f0205042701017097782c@mail.gmail.com> (raw)
In-Reply-To: <87k6mp9uv8.fsf@dedasys.com>
Hi David,
On 26 Apr 2005 21:54:35 +0200, David N. Welton <davidw@dedasys.com> wrote:
> Oh, I most certainly will polish the code as much as possible should
> it prove of interest, but I think what needs vetting is the idea
> itself, which I described clearly in english in a subsequent email.
> If the idea itself stinks, I'm happy to drop it before spending time
> playing around with indentation and other niceties.
But see, that's the problem. You think _other people_ should spend
time reviewing your work first so _you_ don't have to waste time.
Unfortunately, it looks to me like no one is willing to spend their
time reviewing a patch which (a) does not follow
Documentation/CodingStyle and (b) is not submitted as per
Documentation/SubmittingPatches.
I mean, how much work is it to run you code through scripts/Lindent
and drop those awful function banner comments and resend the patch?-)
Pekka
prev parent reply other threads:[~2005-04-27 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 18:05 rootdelay David N. Welton
2005-04-01 18:27 ` rootdelay Daniel Drake
2005-04-25 9:45 ` rootdelay David N. Welton
2005-04-25 14:42 ` rootdelay William Park
2005-04-25 21:34 ` rootdelay David N. Welton
2005-04-29 18:34 ` rootdelay William Park
2005-05-03 8:07 ` rootdelay David N. Welton
2005-05-03 11:13 ` rootdelay David Welton
2005-04-26 10:11 ` rootdelay Pekka Enberg
2005-04-26 19:54 ` rootdelay David N. Welton
2005-04-27 8:01 ` 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=84144f0205042701017097782c@mail.gmail.com \
--to=penberg@gmail.com \
--cc=davidw@dedasys.com \
--cc=dsd@gentoo.org \
--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