RE: KTODO automated TODO lists

["Bird, Tim" <Tim.Bird@sony.com>]

> -----Original Message-----
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> On Thu, Oct 19, 2023 at 2:50 PM Linus Walleij <linus.walleij@linaroorg> wrote:
> > On Thu, Oct 19, 2023 at 6:11 AM Dan Carpenter <dan.carpenter@linaroorg> 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.

You can also create dashboards for people to measure the amount of
desired work outstanding, and to easily find it.  I do something similar
with my own projects (but with a FIXTHIS: prefix)

> > >
> > > lei q -I https://lore.kernel.org/all/
> dKdTl7e3y1zlxphutZsrG0BoJ1YQRFA--MRHazjWXrH4QqVG0Hrp$ -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.
> 
> And if people use appropriate Closes: tags, someone can write a tool
> to only list non-closed items.

Wouldn't you remove the "KTODO:" and alter the comment (or remove it), with
the commit that closed the issue?  It seems like leaving the KTODO would
be a bug, as it no longer applies and would be confusing.

 -- Tim