On Thu, 2 Jul 2009, Justin P. Mattock wrote:No my intentions were not to eat reviewer bandwidth, or get in the way.
No I will not be afraid of submitting patches, and having them be rejected.
all part of the learning curve.
I'd suggest generally not starting out with spelling, grammatical and
formatting patches. It eats reviewer bandwidth, perturbs the codebase
(causing people working on it to have to update their code) and does not
give you as much opportunity to to learn about the code.
Try fixing smaller, known bugs or adding small useful changes.Thanks for this, Ill have to give this a look and see.
The TODO list for the SELinux kernel code is here:
http://selinuxproject.org/page/Kernel_Development
You can also email the maintainers and ask for suggestions on what toalright James,
tackle.
- James