From: "Duje Mihanović" <duje.mihanovic@skole.hr>
To: "Joe Perches" <joe@perches.com>, "Alvin Šipraga" <alvin@pqrs.dk>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Alvin Šipraga" <alsi@bang-olufsen.dk>
Subject: Re: [PATCH] get_maintainer: correctly parse UTF-8 encoded names in files
Date: Mon, 16 Oct 2023 16:37:26 +0200 [thread overview]
Message-ID: <5719647.DvuYhMxLoT@radijator> (raw)
In-Reply-To: <20231014-get-maintainers-utf8-v1-1-3af8c7aeb239@bang-olufsen.dk>
On Saturday, October 14, 2023 7:22:44 PM CEST Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> While the script correctly extracts UTF-8 encoded names from the
> MAINTAINERS file, the regular expressions damage my name when parsing
> from .yaml files. Fix this by replacing the Latin-1-compatible regular
> expressions with the unicode property matcher \p{Latin}. It's also
> necessary to instruct Perl to open all files with UTF-8 encoding.
>
> The issue was also identified on the b4 mailing list [1]. This should
> solve the observed side effects there as well.
>
> Link: https://lore.kernel.org/all/20230726-gush-slouching-a5cd41@meerkat/
[1]
> Signed-off-by: Alvin Šipraga <alsi@bang-olufsen.dk>
> ---
> scripts/get_maintainer.pl | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Tested-by: Duje Mihanović <duje.mihanovic@skole.hr>
next prev parent reply other threads:[~2023-10-16 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 17:22 [PATCH] get_maintainer: correctly parse UTF-8 encoded names in files Alvin Šipraga
2023-10-16 14:37 ` Duje Mihanović [this message]
2023-10-16 22:17 ` Joe Perches
2023-10-16 23:56 ` Alvin Šipraga
2023-12-14 1:06 ` Alvin Šipraga
2023-12-14 1:41 ` Linus Torvalds
2023-12-14 14:57 ` Alvin Šipraga
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=5719647.DvuYhMxLoT@radijator \
--to=duje.mihanovic@skole.hr \
--cc=alsi@bang-olufsen.dk \
--cc=alvin@pqrs.dk \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@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