* Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> [231019 09:21]: > 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. > > > > > > 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. > > And if people use appropriate Closes: tags, someone can write a tool > to only list non-closed items. Could the tool also look at potential git commits to the affected function if Closes is lacking (potential opened issues)? Sort of like the stable kernel failed to apply patch emails list potential patches that may also be needed? We all try our best to have closes tags, etc but sometimes they are missed. Thanks, Liam
