From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending
Date: Tue, 17 Mar 2026 13:33:03 +0100 [thread overview]
Message-ID: <cover.1773750701.git.linux@leemhuis.info> (raw)
This patch-set tweaks a few parts in the fringes of our text on bug
reporting while replacing two sections at the end with a new text as
proper appendix that hopefully better fits the purpose and covers more
aspects.
This is the first versions of this patch-set, but it starts as v2, as it
contains three patches and a few bits that were part of an earlier and
bigger patch-set. This incorporates review feedback given there. The
last patch in this series is mostly new, but includes a few bits from
patch 4 and 5 of the earlier series.
Ciao, Thorsten
v2:
- initial version with 3 patches taken from this abandoned patch-set:
https://lore.kernel.org/all/cover.1761481839.git.linux@leemhuis.info/
- Rewrite the section at the end and make it a proper appendix; based
on patches 4 and 5 from above patch-set
- Incorporate various mostly minor review feedback. Among them:
- Drop the change switching from single to double quotes.
- Point out that feedback can be sent as a patch, too – and add a
patch to sync the text about feedback with two other documents that
contain a para which this section is based on.
Thorsten Leemhuis (5):
docs: reporting-issues: mention text is best viewed rendered
docs: reporting-issues: tweak the reference section intro
docs: reporting-issues: add conclusion to the step-by-step guide
docs: verify-bugs-… and quickly-build-…: improve feedback section
docs: reporting-issues: create a proper appendix explaining
specialties
.../quickly-build-trimmed-linux.rst | 14 +-
.../admin-guide/reporting-issues.rst | 210 +++++++++---------
.../verify-bugs-and-bisect-regressions.rst | 15 +-
3 files changed, 123 insertions(+), 116 deletions(-)
base-commit: 73f175a46330c57ab5797287233cbf83a36b6a99
--
2.53.0
next reply other threads:[~2026-03-17 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 12:33 Thorsten Leemhuis [this message]
2026-03-17 12:33 ` [PATCH v2 1/5] docs: reporting-issues: mention text is best viewed rendered Thorsten Leemhuis
2026-03-17 12:33 ` [PATCH v2 2/5] docs: reporting-issues: tweak the reference section intro Thorsten Leemhuis
2026-03-17 12:33 ` [PATCH v2 3/5] docs: reporting-issues: add conclusion to the step-by-step guide Thorsten Leemhuis
2026-03-17 12:33 ` [PATCH v2 4/5] docs: verify-bugs-… and quickly-build-…: improve feedback section Thorsten Leemhuis
2026-03-17 12:33 ` [PATCH v2 5/5] docs: reporting-issues: create a proper appendix explaining specialties Thorsten Leemhuis
2026-03-17 17:17 ` [PATCH v2 0/5] docs: reporting-issues: tweak a few areas and rewrite the ending Jonathan Corbet
2026-03-22 20:48 ` Jonathan Corbet
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.1773750701.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=regressions@lists.linux.dev \
/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.