From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] docs: reporting-issues: a easier process for reporting stable regressions
Date: Sun, 7 Mar 2021 12:33:48 +0100 [thread overview]
Message-ID: <cover.1615116592.git.linux@leemhuis.info> (raw)
This series creates a streamlined process for users wanting to report
regressions within a stable and longterm kernel series. The existing process is
too demanding, complicated and takes too much time for this case.
I didn't CC the stable maintainers here, they need to review the whole document
anyway once the last few details have been sorted out.
v2:
* inital version, starting straight with v2 to avoid confusion, as one of the
patches was submitted earlier already
Thorsten Leemhuis (2):
docs: reporting-issues.rst: move tainted check upwards
docs: reporting-issues.rst: shortcut for reporting stable regressions
.../admin-guide/reporting-issues.rst | 222 +++++++++++-------
1 file changed, 135 insertions(+), 87 deletions(-)
base-commit: ba5cb300e0b540a330d579402d72cdd1808e5a8f
--
2.29.2
next reply other threads:[~2021-03-07 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 11:33 Thorsten Leemhuis [this message]
2021-03-07 11:33 ` [PATCH v2 1/2] docs: reporting-issues.rst: move tainted check upwards Thorsten Leemhuis
2021-03-07 11:33 ` [PATCH v2 2/2] docs: reporting-issues.rst: shortcut for reporting stable regressions Thorsten Leemhuis
2021-03-15 20:11 ` Jonathan Corbet
2021-03-19 19:39 ` 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=cover.1615116592.git.linux@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.