From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v2] MAINTAINERS: add Documentation/dev-tools/ to workflows@
Date: Mon, 29 Jul 2024 15:29:47 -0600 [thread overview]
Message-ID: <87ttg7999w.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240723223258.2197852-1-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> The goal of the workflows@ mailing list was to make it easier for
> maintainers who don't use lore+lei to subscribe to topics related
> to process changes. In other words it should cover changes to Documentation
> files which most maintainers should know about. Recent changes from Kees [1]
> to provide guidelines on naming KUnit files did not fall under workflows@
> since Documentation/dev-tools/ isn't covered. The patch volume for
> dev-tools isn't huge and most of the changes are interesting. Add it.
>
> Link: https://lore.kernel.org/20240720165441.it.320-kees@kernel.org/ # [1]
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Kees Cook <kees@kernel.org>
> ---
> v2:
> - s/workloads/workflows/
> v1: https://lore.kernel.org/all/20240722142913.1709594-1-kuba@kernel.org/
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ec6904cbfd1f..a85234de4fd0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6680,6 +6680,7 @@ DOCUMENTATION PROCESS
> M: Jonathan Corbet <corbet@lwn.net>
> L: workflows@vger.kernel.org
> S: Maintained
> +F: Documentation/dev-tools/
> F: Documentation/maintainer/
Applied, thanks.
jon
prev parent reply other threads:[~2024-07-29 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 22:32 Jakub Kicinski
2024-07-29 21:29 ` Jonathan Corbet [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=87ttg7999w.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--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