From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Project in Kernel Development
Date: Thu, 25 May 2006 08:45:27 +0000 [thread overview]
Message-ID: <44756EA7.50301@bfs.de> (raw)
In-Reply-To: <d5b9712e0605220237j4085ce7i9d35b081d3cd0ac1@mail.gmail.com>
Dear avinash,
thanks for your interest in our project. I guess your are searching for
a test bed for new ideas that came up when your working on your courses.
That is ok and the linux kernel is a very nice test case as several
other project had found.
Unfortunately the kernel janitors project is quit the opposite, we do
not introduce new features but try to prevent bitrot in the sources.
looking after warning and compile errors, replacing obsolete functions
and so on.
i do not know what your college expects but if you can out-line your
interests and there requirements we can find a solution. Even one that
may have nothing to do with kernel development. You may think that's
boring but remember the toolschain, documentation, testing, ....
All the things you need BEFORE you can even start doing kernel development.
re,
wh
avinash pawar wrote:
> Hi All,
>
> I am a MTech student and looking for project in Kernel Development.
> May i get some Kernel Development work which i can submit as Project
> Work in
> my college.
>
> regards,
> Avinash
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/kernel-janitors
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2006-05-25 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 9:49 [KJ] Project in Kernel Development avinash pawar
2006-05-25 8:45 ` walter harms [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=44756EA7.50301@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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 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.