From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lbulwahn@redhat.com>,
Akira Yokosawa <akiyks@gmail.com>,
linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: repair file entry in DOCUMENTATION
Date: Wed, 24 Apr 2024 13:15:52 -0600 [thread overview]
Message-ID: <87v846shav.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240417101429.240495-1-lukas.bulwahn@redhat.com>
Lukas Bulwahn <lbulwahn@redhat.com> writes:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit 1e596d5eff3d ("docs: Detect variable fonts and suggest denylisting
> them") adds the new script check-variable-fonts.sh and intends to refer to
> it in the DOCUMENTATION section in MAINTAINERS. However, the file entry
> refers to scripts/check-variable-font.sh. Note the missing "s".
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
>
> Repair this new file entry in the DOCUMENTATION section.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4356b28ce625..250c8f8caa08 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6493,7 +6493,7 @@ S: Maintained
> P: Documentation/doc-guide/maintainer-profile.rst
> T: git git://git.lwn.net/linux.git docs-next
> F: Documentation/
> -F: scripts/check-variable-font.sh
> +F: scripts/check-variable-fonts.sh
> F: scripts/documentation-file-ref-check
Applied, thanks.
jon
prev parent reply other threads:[~2024-04-24 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 10:14 [PATCH] MAINTAINERS: repair file entry in DOCUMENTATION Lukas Bulwahn
2024-04-17 13:46 ` Akira Yokosawa
2024-04-24 19:15 ` 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=87v846shav.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
/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 NNTP newsgroup(s).