From: Jesper Juhl <jesper.juhl@gmail.com>
To: regatta <regatta@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to be a kernel developer ?
Date: Tue, 19 Jul 2005 03:24:59 +0200 [thread overview]
Message-ID: <9a8748490507181824432e498b@mail.gmail.com> (raw)
In-Reply-To: <9a87484905071818116f7cb0de@mail.gmail.com>
On 7/19/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 7/18/05, regatta <regatta@gmail.com> wrote:
> > Hi
> >
> > I want to join the Kernel community and help in developing Linux
> > kernel, I'm good in C,Perl and not that good in C++
> >
> The kernel is written in (mainly) C and (a little bit of) asm, no C++ in there.
>
> > is there any How-To page in how to help or how to join ? since I want
> > to start in basic things
> >
> A few things you should do :
>
[snip]
A few things I forgot to mention in the first mail.
You can also help out by testing the development kernels - they need
testing by as many people as possible, so start testing the -rc
kernels and the daily git snapshots as well as the -mm kernels. Test
if they build with your usual configuration, test if they build with
"allnoconfig", "allyesconfig", "allmodconfig" and perhaps a random
config or two. Test if they boot OK, if they run OK for a longer time,
etc.
When you find a problem you can try to fix the issue yourself and send
a patch to both the mailinglist and the person responsible for the
code in question. If you are unable to fix the problem yourself, then
send a detailed bugreport to the list and the person responsible for
the code. Take a look at the REPORTING-BUGS file in the kernel source
dir and the Documentation/BUG-HUNTING file.
Helping to test pre-release kernels is a valuable effort. Run a new
kernel daily :-)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-07-19 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 14:35 how to be a kernel developer ? regatta
2005-07-18 14:43 ` Alejandro Bonilla
2005-07-18 16:22 ` Andrew Ruder
2005-07-19 1:11 ` Jesper Juhl
2005-07-19 1:24 ` Jesper Juhl [this message]
2005-07-19 21:53 ` how to be (SAFE) " Brian O'Mahoney
2005-07-19 23:02 ` Jan Blunck
2005-07-20 0:25 ` Jesper Juhl
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=9a8748490507181824432e498b@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regatta@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.