From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Stuff for kernel janitors to do
Date: Fri, 07 Mar 2014 08:28:04 +0000 [thread overview]
Message-ID: <20140307082804.GD29018@mwanda> (raw)
We always get people asking for ideas. It would be nice if we could
start taking care of kernel bugzilla. I have wanted to do this but in
the end I got distracted.
Or here is another idea that might be fun. Instead of directing people
to staging we could take over one specific staging driver and focus on
it. It would be a good laugh to swarm all over one driver.
regards,
dan carpenter
reply other threads:[~2014-03-07 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140307082804.GD29018@mwanda \
--to=dan.carpenter@oracle.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