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 6/6] docs: 6.Followthrough.rst: advice on handling regressions fixes
Date: Fri, 13 Dec 2024 09:30:46 -0700 [thread overview]
Message-ID: <871pybwnnt.fsf@trenco.lwn.net> (raw)
In-Reply-To: <e7344ff7a57b61380152defaa5ec13f06ac5d7d0.1733825632.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Add some advice on how to handle regressions as developer, reviewer, and
> maintainer, as resolving regression without unnecessary delays requires
> multiple people working hand in hand.
>
> This removes equivalent paragraphs from a section in
> Documentation/process/handling-regressions.rst, which will become mostly
> obsolete through this and follow-up changes.
>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
> Documentation/process/6.Followthrough.rst | 24 ++++++++++++++++---
> .../process/handling-regressions.rst | 16 -------------
> 2 files changed, 21 insertions(+), 19 deletions(-)
Nothing really to complain about here (though I do worry a bit about the
idea that calling something a regression fix allows bypassing all of our
usual testing).
Thanks,
jon
next prev parent reply other threads:[~2024-12-13 16:30 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
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 [this message]
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=871pybwnnt.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.