From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Subject: Re: [tools] [b4] some issues with b4 ty $fromname
Date: Thu, 7 May 2020 11:57:45 -0400 [thread overview]
Message-ID: <20200507155745.rgdivy34t4oxwd4y@chatter.i7.local> (raw)
In-Reply-To: <20200507125054.GA19511@e121166-lin.cambridge.arm.com>
On Thu, May 07, 2020 at 01:50:54PM +0100, Lorenzo Pieralisi wrote:
> Hi,
>
> I have just run into a name formatting issue with b4 ty command, email
> message generated (as an example) attached ($fromname garbled), I am
> sure it is a pretty trivial set-up issue with email encoding and my
> python environment, please let me know if that's something easy to fix
> and thank you very much for this very useful tool.
Thanks for the report -- this is now fixed in master and stable-0.4.y.
Note: this data is recorded at "b4 am" time, so fixes will only show up
for new series/patches you fetch with "b4 am".
Best regards,
-K
prev parent reply other threads:[~2020-05-07 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 12:50 [b4] some issues with b4 ty $fromname Lorenzo Pieralisi
2020-05-07 15:57 ` Konstantin Ryabitsev [this message]
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=20200507155745.rgdivy34t4oxwd4y@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--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 NNTP newsgroup(s).