From: Randy Dunlap <rdunlap@infradead.org>
To: Jakub Kicinski <kuba@kernel.org>, corbet@lwn.net
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH docs v2] MAINTAINERS: treat Documentation/maintainer as process docs
Date: Thu, 13 Jul 2023 16:14:29 -0700 [thread overview]
Message-ID: <001d94a5-6afa-98cb-3b2f-05711ae309d0@infradead.org> (raw)
In-Reply-To: <20230713230713.1505561-1-kuba@kernel.org>
Hi,
On 7/13/23 16:07, Jakub Kicinski wrote:
> A handful of people got caught out by the recent changes in git
> which changed the format of Message-ID and broke our recommended
> applyhook for adding lore links.
>
> This was fixed in the docs by commit 2bb19e740e9b ("Documentation:
> update git configuration for Link: tag") but it seems like few people
> have noticed. Add maintainer directory to the process entry so that
> workflows@ gets CCed.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
Not your problem, but I find "DOCUMENTATION PROCESS" confusing.
It's not about the documentation process. IMO it needs a colon
at least:
DOCUMENTATION: PROCESS
or
DOCUMENTATION: DEVELOPMENT PROCESS
> ---
> v2:
> - fix order of entries
> v1: https://lore.kernel.org/all/20230712161011.1339829-1-kuba@kernel.org/
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3be1bdfe8ecc..fff7e50948b6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6206,6 +6206,7 @@ DOCUMENTATION PROCESS
> M: Jonathan Corbet <corbet@lwn.net>
> L: workflows@vger.kernel.org
> S: Maintained
> +F: Documentation/maintainer/
> F: Documentation/process/
>
> DOCUMENTATION REPORTING ISSUES
--
~Randy
next prev parent reply other threads:[~2023-07-13 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 23:07 Jakub Kicinski
2023-07-13 23:14 ` Randy Dunlap [this message]
2023-07-14 18:16 ` 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=001d94a5-6afa-98cb-3b2f-05711ae309d0@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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