From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
workflows@vger.kernel.org, regressions@lists.linux.dev,
linux-doc@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/6] docs: more detailed instructions on handling regressions
Date: Fri, 13 Dec 2024 09:14:50 -0700 [thread overview]
Message-ID: <87msgzwoed.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aed019088599c6dc8aab8879dfda35785e01d316.1733825632.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Add a few more specific guidelines on handling regressions to the
> kernel's two most prominent guides about contributing to Linux, as
> developers apparently work with quite different interpretations of what
> Linus expects.
>
> Changes like this were asked for during the Maintainers Summit 2024. The
> four rules of thumb spelled out are all closely based on statements
> Linus made there; LWN documented all except "Expedite fixing regressions
> that reached a release deemed for end users.." in their coverage [1].
"deemed" used in this way is a bit strange. "intended" perhaps?
> +On timing:
> +
> + - Expedite fixing regressions that reached releases deemed for end users
> + through new mainline releases or stable backports during the past year.
Here too.
That little nit is all I can find to complain about in this one, though
:)
jon
next prev parent reply other threads:[~2024-12-13 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 10:15 [PATCH v1 0/6] docs: add instruction about handling regressions to our core texts for contributors Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 1/6] docs: more detailed instructions on handling regressions Thorsten Leemhuis
2024-12-13 16:14 ` Jonathan Corbet [this message]
2024-12-20 12:17 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 2/6] docs: 6.Followthrough.rst: when to involved Linus in regressions Thorsten Leemhuis
2024-12-13 16:17 ` Jonathan Corbet
2024-12-20 12:41 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 3/6] docs: 6.Followthrough.rst: interaction with stable wrt to regressions Thorsten Leemhuis
2024-12-13 16:20 ` Jonathan Corbet
2024-12-20 13:13 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 4/6] docs: 6.Followthrough.rst: tags to use in regressions fixes Thorsten Leemhuis
2024-12-13 16:24 ` Jonathan Corbet
2024-12-20 13:18 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 5/6] docs: 6.Followthrough.rst: more specific advice on fixing regressions Thorsten Leemhuis
2024-12-13 16:28 ` Jonathan Corbet
2024-12-20 14:21 ` Thorsten Leemhuis
2024-12-10 10:15 ` [PATCH v1 6/6] docs: 6.Followthrough.rst: advice on handling regressions fixes Thorsten Leemhuis
2024-12-13 16:30 ` Jonathan Corbet
2024-12-20 14:24 ` Thorsten Leemhuis
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=87msgzwoed.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.