From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: A kernel janitor question
Date: Wed, 15 Oct 2008 18:34:23 +0000 [thread overview]
Message-ID: <48F637AF.60202@bfs.de> (raw)
In-Reply-To: <ee90333f0810141017i5907bc48jfd67cc909e2dbff3@mail.gmail.com>
David Li schrieb:
> The requirement that I am not about sure about is if the kernel
> janitor needs to be able to build, configure and boot up a customized
> kernel in order to test his patches. It seems to me a must. What's the
> common practice in this for everyone? Are there any specific
> requirements on HW? Can any experienced janitors share some thoughts?
The answer depends on the situation. for some patches you need special hardware
so it should be the responsibility of the current subsystem maintainer to make
sure it works on it.
As janitor you have to compile-test the fixes at least and you should follow the thread
that means if the maintainer says "you patch is bad because the documentation is faulty
not the program." you should fix the documentation in the next step not leave it as it is.
re,
wh
next prev parent reply other threads:[~2008-10-15 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 17:17 A kernel janitor question David Li
2008-10-15 18:34 ` walter harms [this message]
2008-10-18 1:13 ` Ian Hilt
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=48F637AF.60202@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.