tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: tools@linux.kernel.org, konstantin@linuxfoundation.org
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: Re: [tools] b4: UTF-8 in replies
Date: Thu, 1 Oct 2020 19:09:48 +0100	[thread overview]
Message-ID: <20201001180948.GU6715@sirena.org.uk> (raw)
In-Reply-To: <20201001180541.poupp36rtajzkihs@chatter.i7.local>

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

On Thu, Oct 01, 2020 at 02:05:41PM -0400, Konstantin Ryabitsev wrote:
> On Thu, Oct 01, 2020 at 07:14:05PM +0200, Michał Mirosław wrote:

> > The bug is that when generating the reply, script doesn't include MIME
> > headers but is using UTF-8 in the body (eg. when replying to an author
> > with non-US name, like me).

> Hm... is that causing you any problems? We make sure to set 
> "Content-Transfer-Encoding: 8bit" in the headers, so unless you're using 
> some extremely old SMTP software, UTF-8 in the body or headers shouldn't 
> matter.

vger doesn't like 8 bit content in the headers.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  reply	other threads:[~2020-10-01 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201001171405.GA17873@qmqm.qmqm.pl>
2020-10-01 18:05 ` b4: UTF-8 in replies Konstantin Ryabitsev
2020-10-01 18:09   ` Mark Brown [this message]
2020-10-01 18:36   ` Michał Mirosław
2020-10-01 18:41     ` Michał Mirosław
2020-10-01 19:26       ` Konstantin Ryabitsev
2020-10-02 21:09         ` [tools] " Mark Brown
2020-10-03 10:13           ` Michał Mirosław
2020-10-03 10:18             ` Michał Mirosław
2020-10-03 14:40               ` Konstantin Ryabitsev

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=20201001180948.GU6715@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --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).