From: Thorsten Leemhuis <email@example.com>
To: Lukas Bulwahn <firstname.lastname@example.org>
Cc: "open list:DOCUMENTATION" <email@example.com>,
Linus Torvalds <firstname.lastname@example.org>,
Greg Kroah-Hartman <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Randy Dunlap <email@example.com>,
Jonathan Corbet <firstname.lastname@example.org>
Subject: Re: [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions
Date: Tue, 4 Jan 2022 14:29:44 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 04.01.22 13:16, Lukas Bulwahn wrote:
> On Mon, Jan 3, 2022 at 3:23 PM Thorsten Leemhuis <firstname.lastname@example.org> 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):
(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 <email@example.com>
next prev parent reply other threads:[~2022-01-04 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 9:50 [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Thorsten Leemhuis
2022-01-03 9:50 ` [RFC PATCH v1 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-03 17:07 ` Jakub Kicinski
2022-01-03 17:20 ` Thorsten Leemhuis
2022-01-03 17:55 ` Jakub Kicinski
2022-01-04 14:17 ` Lukas Bulwahn
2022-01-04 17:57 ` Thorsten Leemhuis
2022-01-05 8:45 ` Lukas Bulwahn
2022-01-03 9:50 ` [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-04 12:16 ` Lukas Bulwahn
2022-01-04 13:29 ` Thorsten Leemhuis [this message]
2022-01-04 14:42 ` Jonathan Corbet
2022-01-04 15:09 ` Randy Dunlap
2022-01-04 18:02 ` Thorsten Leemhuis
2022-01-03 14:01 ` [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Greg Kroah-Hartman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).