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: Re: b4 is having trouble with unicode emails
Date: Thu, 22 Sep 2022 14:59:13 -0700	[thread overview]
Message-ID: <YyzasbZ80Osek12a@google.com> (raw)
In-Reply-To: <20220922214840.fw7kdyjidsp2g4vi@meerkat.local>

On Thu, Sep 22, 2022 at 05:48:40PM -0400, Konstantin Ryabitsev wrote:
> On Thu, Sep 22, 2022 at 02:10:34PM -0700, Dmitry Torokhov wrote:
> > Hi Konstantin,
> > 
> > It looks like b4 does not like non-acsii in emails, and fails for emails
> > like "Marek Behún <kabel@kernel.org>":
> 
> It wasn't really the unicode, we just weren't expecting to receive fully
> formatted addresses like that. E.g., this was fine:
> 
>     b4 send --to foo@example.com
> 
> but this wasn't:
> 
>     b4 send --to 'Foo Foo <foo@example.com>'
> 
> The latest master/stable-0.10.y should have handle this properly.

No, if you look closely in my log there were 2 invocations, one with

	--to 'Marek Behún <kabel@kernel.org>'

which dies with UnicodeEncodeError exception, while another, with

	--to='Marek Behun <kabel@kernel.org>'

works properly.

This is with ToT checkout at:

6c215d8 ez: don't send a cover letter for a 1-patch series

Thanks.

-- 
Dmitry

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 21:10 b4 is having trouble with unicode emails Dmitry Torokhov
2022-09-22 21:48 ` Konstantin Ryabitsev
2022-09-22 21:59   ` Dmitry Torokhov [this message]
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=YyzasbZ80Osek12a@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.