From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Request for an updated to-do list
Date: Fri, 08 Nov 2013 08:15:02 +0000 [thread overview]
Message-ID: <20131108081502.GX26669@mwanda> (raw)
In-Reply-To: <CAAL8FfB_k11U41U44+yHUgxBBap8xLUScX6UOrSoupG=O92W1A@mail.gmail.com>
These days we just say to pick something from staging and work on it.
Staging is full of a variety of code which is almost ok to code which is
total crap. There are security bugs, locking bugs, every single type of
bug you can imagine all the way down to white space messiness.
regards,
dan carpenter
prev parent reply other threads:[~2013-11-08 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 20:30 Request for an updated to-do list Luca Bartolacci
2013-11-05 20:34 ` Julia Lawall
2013-11-08 8:15 ` Dan Carpenter [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=20131108081502.GX26669@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