On 04.01.22 13:16, Lukas Bulwahn wrote: > On Mon, Jan 3, 2022 at 3:23 PM Thorsten Leemhuis <linux@xxxxxxxxxxxxx> wrote: >> diff --git a/Documentation/admin-guide/regressions.rst b/Documentation/admin-guide/regressions.rst >> index 1ff6a0802fc9..5f02a001e53c 100644 >> --- a/Documentation/admin-guide/regressions.rst >> +++ b/Documentation/admin-guide/regressions.rst >> @@ -63,6 +63,10 @@ list; add the aforementioned paragraph, just omit the caret (the ^) before the >> ``introduced``, which make regzbot treat your mail (and not the one you reply >> to) as the report. >> >> +Try to fix regressions quickly once the culprit got identified. Fixes for most > > s/got/gets/ --- at least, that is what the gmail grammar spelling suggests :) Hmm, LanguageTool didn't complain. Not totally sure, maybe both approaches are okay. But the variant suggested by the gmail checker might be the better one. You comment made me put my text in google docs, which found about fifteen other places where something was wrong. Should have done this sooner, sorry. :-/ > [a lot of helpful comments] Many thx, fixed all of them locally. > Thorsten, thanks for this process documentation. It was a nice and > comprehensible read for me. Let us hope it helps contributors and > maintainers to adopt those recommendations. Time will tell. Guess it will take a while. > If you need any support of any kind (more contributors, If you known people looking for a kernel docs text to work on, I have two related ideas that might be of interest for them: * the kernel docs IMHO could need a text explaining how to use "make localmodconfig" to ordinary users -- for example, when preparing for a bisection or a quick test of the latest mainline tree. Something like this maybe, but modernized (and maybe with a explanation how to clone the tree without getting the history from ten years ago): http://www.h-online.com/open/features/Good-and-quick-kernel-configuration-creation-1403046.html (that's a translation of a German text I wrote a decade ago...) * the kernel docs contain a text explaining bisection, but it iirc is brief and quite hard to understand for users that are new to this. That's why I think it would be wise to improve or even rewrite the text, to make it more accessible. > financial support) for such further > documentation on the development process, please reach out to me and I > will see what I can do. Sounds great. I might do that sooner or later for the two ideas I outlined above, but that is unlikely to happen in the next few months. > Reviewed-by: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx> Great, thx! Ciao, Thorsten
