From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jerry <Jerry@jrr.cz>
Cc: Johan Hovold <johan@kernel.org>, linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/1] usbserial: cp210x - icount support for parity error checking
Date: Mon, 22 Jun 2020 07:30:54 +0200 [thread overview]
Message-ID: <20200622053054.GA134804@kroah.com> (raw)
In-Reply-To: <c9b58c7f-e40a-0988-6b7d-15beac7219de@jrr.cz>
On Mon, Jun 22, 2020 at 06:38:13AM +0200, Jerry wrote:
> Greg Kroah-Hartman wrote on 6/21/20 3:58 PM:
> > Please use unicode (well utf-8 if possible), I'm all for that, there is
> > no requirement to use ascii only for your name in patches. I wish more
> > people would do that when needed, as it's only fair to them to be able
> > to properly represent their names and not have to change them somehow.
> I tried it and it seems that www.spinics.net understand UTF-8 but at
> marc.info it doesn't work correctly.
> https://marc.info/?l=linux-usb&m=159279589104617
Why care about marc.info? We don't control that, nor do we use it.
If lore.kernel.org does not work, please let us know, we can fix that.
> It seems that this page don't send correct encoding to web browser so
> Firefox uses windows-1252 and insted of capital S with caron I can see A
> with ring. Similarily insted of I with acute accent the browser shows A with
> tilda... it looks horible. And even if I force UTF8 encoding for view, it
> corrects mail From but my name at Signed-off-by line stays damaged.
>
> So UTF-8 seems be a bad idea for kernel mailling list.
It should not be, again, if lore.kernel.org does not work, please let
us know.
thanks,
greg k-h
next prev parent reply other threads:[~2020-06-22 5:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 19:58 [PATCH 1/1] usbserial: cp210x - icount support for parity error checking Jerry
2020-06-21 8:54 ` [PATCH v2] " Jerry
2020-06-21 8:58 ` [PATCH 1/1] " Greg Kroah-Hartman
2020-06-21 9:45 ` Jerry
2020-06-21 9:55 ` Greg Kroah-Hartman
2020-06-21 10:34 ` Jerry
2020-06-21 13:58 ` Greg Kroah-Hartman
2020-06-21 20:21 ` [PATCH v3] " Jaromír Škorpil
2020-06-22 5:31 ` Greg Kroah-Hartman
2020-06-22 15:13 ` [PATCH v4] " Jaromír Škorpil
2020-06-25 4:31 ` Jerry
2020-06-25 6:53 ` Johan Hovold
2020-07-01 15:42 ` Johan Hovold
2020-07-01 19:28 ` Jerry
2020-07-03 7:45 ` Johan Hovold
2020-07-03 15:01 ` Johan Hovold
2020-07-06 11:47 ` Jerry
2020-07-06 13:59 ` Johan Hovold
2020-07-08 21:05 ` Jerry
2020-07-13 10:54 ` Johan Hovold
2020-07-03 18:45 ` Jerry
2020-07-06 7:51 ` Johan Hovold
2020-07-06 9:08 ` Johan Hovold
2020-07-08 21:34 ` [PATCH v5] " Jaromir Skorpil
2020-07-08 22:21 ` Jaromir Skorpil
2020-06-22 4:38 ` [PATCH 1/1] " Jerry
2020-06-22 5:30 ` Greg Kroah-Hartman [this message]
2020-06-22 16:50 ` Jerry
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=20200622053054.GA134804@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jerry@jrr.cz \
--cc=johan@kernel.org \
--cc=linux-usb@vger.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).