From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"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
Subject: Re: [PATCH 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix
Date: Mon, 11 Mar 2024 14:40:51 +0100 [thread overview]
Message-ID: <e73a0418-33ad-470d-8740-97694e6dd6b1@leemhuis.info> (raw)
In-Reply-To: <20240308-regzbot-fixes-v1-2-577a4fe16e12@collabora.com>
Thx for this!
On 08.03.24 15:10, Nícolas F. R. A. Prado wrote:
> On the reference documentation for regzbot, the fixed-by command has
> been renamed to fix. Update the kernel documentation accordingly.
>
> Link: https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
> Link: https://gitlab.com/knurd42/regzbot/-/commit/6d8d30f6bda84e1b711121bb98a07a464d3f089a
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Reviewed-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
> Documentation/process/handling-regressions.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/handling-regressions.rst b/Documentation/process/handling-regressions.rst
> index 42b13f77b019..ce6753a674f3 100644
> --- a/Documentation/process/handling-regressions.rst
> +++ b/Documentation/process/handling-regressions.rst
> @@ -432,7 +432,7 @@ or itself is a reply to that mail:
> * Mark a regression as fixed by a commit that is heading upstream or already
> landed::
>
> - #regzbot fixed-by: 1f2e3d4c5d
> + #regzbot fix: 1f2e3d4c5d
>
> * Mark a regression as a duplicate of another one already tracked by regzbot::
>
>
prev parent reply other threads:[~2024-03-11 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 14:09 [PATCH 0/2] docs: *-regressions.rst: Tweaks to the commands Nícolas F. R. A. Prado
2024-03-08 14:09 ` [PATCH 1/2] docs: *-regressions.rst: Use collon after regzbot introduced command Nícolas F. R. A. Prado
2024-03-11 13:39 ` Thorsten Leemhuis
2024-03-11 13:57 ` Nícolas F. R. A. Prado
2024-03-08 14:10 ` [PATCH 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix Nícolas F. R. A. Prado
2024-03-11 13:40 ` Thorsten Leemhuis [this message]
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=e73a0418-33ad-470d-8740-97694e6dd6b1@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--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.