From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
devel <devel@driverdev.osuosl.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: Tuxradar patching article and [PATCH] scripts/cvt_kernel_style.pl
Date: Wed, 10 Mar 2010 19:32:16 +0100 [thread overview]
Message-ID: <4B97E5B0.5070900@s5r6.in-berlin.de> (raw)
In-Reply-To: <1268177526.1545.62.camel@Joe-Laptop.home>
Joe Perches wrote:
> There was an article published recently:
> http://www.tuxradar.com/content/newbies-guide-hacking-linux-kernel
> that seems to have prompted several new contributors (welcome)
> to create style reformatting patches.
Uh oh. How can a newcomer know what good style is?
Please start your career of kernel contributions differently:
- Test new kernels. Report issues and work with the developers to
get the issues fixed.
- If there is a bug which nags you but there doesn't seem to be
an active developer to fix it anytime soon, try to fix it yourself.
Or if you are aware of a small RFE for a subsystem which interests you
personally, try to implement that small feature.
It doesn't make sense to start kernel development with something which
you are likely not going to connect with personally. (Reformat others'
code? Better write your own code, i.e. a bug fix or a small feature.)
PS:
I am also saying this because I repeatedly see "style fixes" posted
which are questionable at best, or actually degrade style, or even
introduce bugs.
PPS:
How can a script know what good style is?
--
Stefan Richter
-=====-==-=- --== -=-=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2010-03-10 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 23:32 Joe Perches
2010-03-09 23:41 ` Greg KH
2010-03-10 0:06 ` Joe Perches
2010-03-10 0:16 ` Greg KH
2010-03-10 0:34 ` Joe Perches
2010-03-10 18:35 ` Stefan Richter
2010-03-10 18:38 ` Joe Perches
2010-03-10 1:22 ` Frans Pop
2010-03-10 3:25 ` [PATCH V2] scripts/cvt_kernel_style.pl: partial "kernel style" pretty-printing Joe Perches
2010-03-24 20:01 ` [PATCH] scripts/cvt_kernel_style.pl: kernel style source code reformatter Joe Perches
2010-03-24 22:31 ` Frans Pop
2010-03-10 18:32 ` Stefan Richter [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=4B97E5B0.5070900@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=apw@shadowen.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.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®