All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 26 Jul 2023 16:29:55 -0400	[thread overview]
Message-ID: <20230726-gush-slouching-a5cd41@meerkat> (raw)
In-Reply-To: <1940519.PYKUYFuaPT@radijator>

On Mon, Jul 24, 2023 at 12:49:41PM +0200, Duje Mihanović wrote:
> I decided to try using b4 to submit a patchset for adding Marvell PXA1908 ARM 
> SoC support. Having enrolled an existing branch, I ran `b4 prep -c` and got 
> the following error (this is with the -d switch added):

So, there's apparently something very interesting about that final ć in your
name that trips up get_maintainer.pl. For example, run the following:

$ ./scripts/get_maintainer.pl -f Documentation/devicetree/bindings/clock/marvell,pxa1908.yaml

You will get back a byte sequence \x87 where your name should be:

    "<87>" <duje.mihanovic@skole.hr> (in file)

This is because ć is 0xC4 0x87, but I have no idea why get_maintainer.pl trips
up and splits the unicode sequence into two bytes. It seems to want to do that
for anything above base extended ascii (Latin-A).

I can "fix" this in b4 by forcing it to ignore any unrecognized unicode errors
in get_maintainer.pl output, but it's not a real fix for the underlying
problem.

-K

  parent reply	other threads:[~2023-07-26 20:30 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 ` Konstantin Ryabitsev [this message]
2023-07-27 10:02   ` [BUG b4] " Duje Mihanović
2023-07-27 14:42     ` Konstantin Ryabitsev
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=20230726-gush-slouching-a5cd41@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.