ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: ksummit@lists.linux.dev, outreachy@lists.linux.dev,
	 kernel-janitors@vger.kernel.org
Subject: Re: KTODO automated TODO lists
Date: Thu, 19 Oct 2023 14:50:19 +0200	[thread overview]
Message-ID: <CACRpkdbNOmvBg+wHLHcdvp=YE=jYiKKCVWDqs2cMF85rXyv_aQ@mail.gmail.com> (raw)
In-Reply-To: <369bc919-1a1d-4f37-9cc9-742a86a41282@kadam.mountain>

On Thu, Oct 19, 2023 at 6:11 AM Dan Carpenter <dan.carpenter@linaro.org> wrote:

> We could add that kind of
> thing to a todo list by using a KTODO line.
>
> KTODO: add check for failure in function_something()
>
> Then people can look on lore or use lei to find small tasks to work on
> or they could use lei.
>
> lei q -I https://lore.kernel.org/all/ -o ~/Mail/KTODO --dedupe=mid 'KTODO AND rt:6.month.ago..'
>
> Then grep ^KTODO ~/Mail/KTODO -R and cat the filename you want.

I like it! There are too many of these things falling on the floor.
An easy way to stash it on the technological debt hitlist would be
really helpful.

Yours,
Linus Walleij

  reply	other threads:[~2023-10-19 12:50 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  4:11 Dan Carpenter
2023-10-19 12:50 ` Linus Walleij [this message]
2023-10-19 13:21   ` Geert Uytterhoeven
2023-10-19 15:43     ` Liam R. Howlett
2023-10-19 16:30     ` Bird, Tim
2023-10-19 17:34       ` Dan Carpenter
2023-10-19 17:37         ` Bird, Tim
2023-10-19 17:47 ` Konstantin Ryabitsev
2023-10-23 18:49 ` Andrew Morton
2023-10-23 18:55   ` Linus Torvalds
2023-10-23 19:00     ` Geert Uytterhoeven
2023-10-23 19:17       ` Linus Torvalds
2023-10-23 19:29     ` Steven Rostedt
2023-10-23 21:31       ` Paul E. McKenney
2023-10-23 21:44         ` Tony Luck
2023-10-23 22:25           ` Paul E. McKenney
2023-10-23 19:41     ` Konstantin Ryabitsev
2023-10-24  4:58       ` Andrew Morton
2023-10-24 15:28       ` Konstantin Ryabitsev
2023-10-26 21:58         ` Miguel Ojeda
2023-10-23 21:45   ` NeilBrown
2023-10-24  7:19     ` Geert Uytterhoeven
2023-10-24  7:25       ` Laurent Pinchart
2023-10-24  8:42         ` Jani Nikula
2023-10-24  8:52           ` Laurent Pinchart
2023-10-24 12:36         ` Steven Rostedt
2023-10-24 13:12           ` Laurent Pinchart
2023-10-24 15:53   ` Krzysztof Kozlowski
2023-10-24 21:29     ` NeilBrown
2023-10-24 22:05       ` Steven Rostedt
2023-10-25  3:47         ` Paul E. McKenney
2023-10-25 23:45           ` Steven Rostedt
2023-10-25  6:55       ` Geert Uytterhoeven
2023-10-25 21:14         ` NeilBrown
2023-10-25 22:00           ` Randy Dunlap
2023-10-26  4:29           ` Dan Carpenter
2023-10-26  6:56             ` Geert Uytterhoeven
2023-10-25  7:01       ` Krzysztof Kozlowski
2023-10-25 11:45       ` James Bottomley
2023-10-25 16:40         ` Jani Nikula
2023-10-25 18:07           ` James Bottomley
2023-10-25 18:10             ` Steven Rostedt
2023-10-25 19:43               ` Linus Torvalds
2023-10-25 21:19                 ` NeilBrown
2023-10-25 21:17               ` NeilBrown
2023-10-25 18:55         ` Alexey Dobriyan
2023-10-25 19:27           ` Steven Rostedt
2023-10-25 20:03           ` Alexandre Belloni
2023-10-25 21:38         ` NeilBrown
2023-10-23 23:38 ` Gustavo A. R. Silva
2023-10-24  0:07   ` Gustavo A. R. Silva
2023-10-24  2:16   ` Joe Perches
2023-12-11 18:47   ` Steven Rostedt

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='CACRpkdbNOmvBg+wHLHcdvp=YE=jYiKKCVWDqs2cMF85rXyv_aQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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