kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Logan Blyth <mrbojangles3@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Tips for a Newcomer
Date: Sun, 30 Jun 2013 21:19:19 +0000	[thread overview]
Message-ID: <51D0A0D7.4070408@gmail.com> (raw)

Hello list,

I am looking for some tips on starting as a kernel janitor, and I was 
hoping to find out the general work flow that people use. From what I 
can tell, we search through the kernel-next git repo, then either by 
grep, ctags, or some other method? We are looking for things in the 
KernelJanitors/Todo, possibly stuff turned up by sparse? Maybe a 
different static analyser like from clang?

 From there we make sure the patch applys cleanly and mail the 
maintainer, copying the LKML and Kernel-Janitors?

Are there any recommended tutorials / Articles that google doesn't turn up?

             reply	other threads:[~2013-06-30 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 21:19 Logan Blyth [this message]
2013-07-03  7:28 ` Tips for a Newcomer Dan Carpenter
2013-07-25 12:13 ` Logan Blyth
2013-07-25 13:15 ` Darryl L. Pierce
2013-07-25 14:09 ` Dan Carpenter

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=51D0A0D7.4070408@gmail.com \
    --to=mrbojangles3@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).