From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>
Cc: kernel@collabora.com, regressions@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org,
"Chris Bainbridge" <chris.bainbridge@gmail.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: [PATCH v2 0/2] docs: *-regressions.rst: Tweaks to the commands
Date: Mon, 11 Mar 2024 10:36:14 -0400 [thread overview]
Message-ID: <20240311-regzbot-fixes-v2-0-98c1b6ec0678@collabora.com> (raw)
A couple tweaks to the commands in the regression documentation to make
them up-to-date and less confusing.
Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
---
Changes in v2:
- Reworded patch 1:
- s/collon/colon/
- Made title and message more straightforward
- Link to v1: https://lore.kernel.org/r/20240308-regzbot-fixes-v1-0-577a4fe16e12@collabora.com
---
Nícolas F. R. A. Prado (2):
docs: *-regressions.rst: Add colon to regzbot commands
docs: handling-regressions.rst: Update regzbot command fixed-by to fix
Documentation/admin-guide/reporting-regressions.rst | 2 +-
Documentation/process/handling-regressions.rst | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
---
base-commit: 11afac187274a6177a7ac82997f8691c0f469e41
change-id: 20240308-regzbot-fixes-43a28fd4b621
Best regards,
--
Nícolas F. R. A. Prado <nfraprado@collabora.com>
next reply other threads:[~2024-03-11 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 14:36 Nícolas F. R. A. Prado [this message]
2024-03-11 14:36 ` [PATCH v2 1/2] docs: *-regressions.rst: Add colon to regzbot commands Nícolas F. R. A. Prado
2024-03-11 14:36 ` [PATCH v2 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix Nícolas F. R. A. Prado
2024-03-18 9:40 ` [PATCH v2 0/2] docs: *-regressions.rst: Tweaks to the commands 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=20240311-regzbot-fixes-v2-0-98c1b6ec0678@collabora.com \
--to=nfraprado@collabora.com \
--cc=chris.bainbridge@gmail.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).