ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Levente Kurusa <levex@linux.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Wed, 21 May 2014 17:32:47 +0300	[thread overview]
Message-ID: <20140521143247.GB15585@mwanda> (raw)
In-Reply-To: <20140511195011.GD2527@linux.com>

On Sun, May 11, 2014 at 09:50:11PM +0200, Levente Kurusa wrote:
> I gave a talk recently and after the talk people asked me how could
> they start. The problem, they say, is that there really is no central
> TODO list.

I have invented a new email tag for this.  When I think of something to
do then I put it my email:

TODO-list: 2014-05-21: lirc: LIRC_GET_FEATURES API is sometimes ulong and sometimes u32

Then I can `grep ^TODO-list: inbox` and create a TODO list automatically
and anyone else can send stuff as well.

regards,
dan carpenter

  parent reply	other threads:[~2014-05-21 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  5:30 Jason Cooper
2014-05-11 17:57 ` Sebastian Hesselbarth
2014-05-11 19:16   ` Levente Kurusa
2014-05-11 19:26     ` Greg KH
2014-05-11 19:50       ` Levente Kurusa
2014-05-11 20:33         ` Hans Verkuil
2014-05-11 21:35           ` Theodore Ts'o
2014-05-12  8:19             ` Wolfram Sang
2014-05-12  8:38           ` Wolfram Sang
2014-05-12  9:08             ` Li Zefan
2014-05-12  9:40               ` Hans Verkuil
2014-05-12  9:54               ` Wolfram Sang
2014-05-12 13:58             ` Andrew Lunn
2014-05-12 16:08               ` Stephen Hemminger
2014-05-21 14:32         ` Dan Carpenter [this message]
2014-05-12 16:38       ` Jason Cooper
2014-05-12 23:23         ` Greg KH
2014-05-16  3:47           ` Jason Cooper

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=20140521143247.GB15585@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=levex@linux.com \
    /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