All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Balej <balejk@matfyz.cz>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Jonathan Corbet <corbet@lwn.net>,
	regressions@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Cc: balejk@matfyz.cz
Subject: [PATCH 0/2] regressions documentation improvements
Date: Thu, 28 Mar 2024 20:29:14 +0100	[thread overview]
Message-ID: <20240328194342.11760-1-balejk@matfyz.cz> (raw)

Hello,

this small series suggests two (hopefully) improvements for the
regressions-related documentation texts.

The first one is perhaps unnecessarily nitpicky but if nothing else, it
at least adds a missing word.

The other one tries to clarify for future readers a question which was
on my mind through the whole process during my first attempt at
reporting a regression.

Please take a look, I am eager to hear what you think.

Thank you, kind regards,
K. B.

Karel Balej (2):
  docs: *-regressions.rst: unify quoting, add missing word
  docs: handling-regressions.rst: clarify that "Closes:" tags work too

 .../admin-guide/reporting-regressions.rst     | 10 +++---
 .../process/handling-regressions.rst          | 32 ++++++++++---------
 2 files changed, 22 insertions(+), 20 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-03-28 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 19:29 Karel Balej [this message]
2024-03-28 19:29 ` [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word Karel Balej
2024-04-03 14:13   ` Linux regression tracking (Thorsten Leemhuis)
2024-04-10 21:03     ` Jonathan Corbet
2024-03-28 19:29 ` [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too Karel Balej
2024-04-01  8:38   ` Thorsten Leemhuis
2024-04-01 15:19     ` Randy Dunlap
2024-04-02  9:27       ` Thorsten Leemhuis
2024-04-02 10:13         ` Karel Balej
2024-04-03 14:13           ` 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=20240328194342.11760-1-balejk@matfyz.cz \
    --to=balejk@matfyz.cz \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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.