All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: b4 is having trouble with unicode emails
Date: Thu, 22 Sep 2022 14:10:34 -0700	[thread overview]
Message-ID: <YyzPSrTcGliahL+a@google.com> (raw)

Hi Konstantin,

It looks like b4 does not like non-acsii in emails, and fails for emails
like "Marek Behún <kabel@kernel.org>":

dtor@dtor-ws:~/kernel/linux-next (get_gpiod_from_child-remove)$ b4 send --no-sign --not-me-too --to='Marek Behún <kabel@kernel.org>' -o patches/gpiod-from-child
Converted the branch to 4 messages
Populating To/Cc addresses
Will write out messages into patches/gpiod-from-child
Traceback (most recent call last):
  File "/usr/local/google/home/dtor/b4/b4/command.py", line 358, in <module>
    cmd()
  File "/usr/local/google/home/dtor/b4/b4/command.py", line 341, in cmd
    cmdargs.func(cmdargs)
  File "/usr/local/google/home/dtor/b4/b4/command.py", line 86, in cmd_send
    b4.ez.cmd_send(cmdargs)
  File "/usr/local/google/home/dtor/b4/b4/ez.py", line 1268, in cmd_send
    msg.add_header('To', b4.format_addrs(allto))
  File "/usr/local/google/home/dtor/b4/b4/__init__.py", line 2878, in format_addrs
    addrs.add(email.utils.formataddr(pair))  # noqa
  File "/usr/lib/python3.10/email/utils.py", line 91, in formataddr
    address.encode('ascii')
UnicodeEncodeError: 'ascii' codec can't encode character '\xfa' in position 9: ordinal not in range(128)
dtor@dtor-ws:~/kernel/linux-next (get_gpiod_from_child-remove)$ b4 send --no-sign --not-me-too --to='Marek Behun <kabel@kernel.org>' -o patches/gpiod-from-child
Converted the branch to 4 messages
Populating To/Cc addresses
Will write out messages into patches/gpiod-from-child
  0000-get-rid-of-devm_fwnode_get_-index_-gpiod_from_child.eml
  0001-devm_fwnode_get_gpiod_from_child-is-going-away-as-the-name-is-too-unwieldy-let-s-switch-to-using-the-new-devm_fwnode_gpiod_get.eml
  0002-devm_fwnode_get_gpiod_from_child-is-going-away-as-the-name-is-too-unwieldy-let-s-switch-to-using-the-new-devm_fwnode_gpiod_get.eml
  0003-now-that-there-are-no-more-users-of-these-apis-in-the-kernel-we-can-remove-them.eml
---
DRYRUN: Would have sent 4 messages

Thanks!

-- 
Dmitry

             reply	other threads:[~2022-09-22 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 21:10 Dmitry Torokhov [this message]
2022-09-22 21:48 ` b4 is having trouble with unicode emails Konstantin Ryabitsev
2022-09-22 21:59   ` Dmitry Torokhov
2022-09-22 22:11     ` Konstantin Ryabitsev
2022-09-23 16:47       ` Dmitry Torokhov

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=YyzPSrTcGliahL+a@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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.