From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: tools@linux.kernel.org
Subject: Re: [BUG b4] Encoding issues with --auto-to-cc
Date: Thu, 27 Jul 2023 10:42:50 -0400 [thread overview]
Message-ID: <20230727-demise-fruit-52aab8@meerkat> (raw)
In-Reply-To: <1858953.tdWV9SEqCh@radijator>
On Thu, Jul 27, 2023 at 12:02:16PM +0200, Duje Mihanović wrote:
> I think it's wrong to say get_maintainer splits up the unicode sequence, it
> straight up ignores the first half of the sequence. Perhaps I should file a
> bug for get_maintainer.pl?
Yes, you should report the bug for sure. As you can tell from your originally
submitted series, it's manifested itself multiple times already:
To: =?UTF-8?q?=87?= <duje.mihanovic@skole.hr>
-K
next prev parent reply other threads:[~2023-07-27 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 10:49 [BUG b4] Encoding issues with --auto-to-cc Duje Mihanović
2023-07-26 19:48 ` Konstantin Ryabitsev
2023-07-26 19:54 ` Kernel.org Bugbot
2023-07-26 20:29 ` [BUG b4] " Konstantin Ryabitsev
2023-07-27 10:02 ` Duje Mihanović
2023-07-27 14:42 ` Konstantin Ryabitsev [this message]
2023-07-26 20:37 ` Kernel.org Bugbot
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=20230727-demise-fruit-52aab8@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=duje.mihanovic@skole.hr \
--cc=tools@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).