From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] proc: fixup (c) sign
Date: Wed, 11 Apr 2018 15:41:26 -0700 [thread overview]
Message-ID: <CA+55aFxrpn=GdgqgrczUdj-wndFdQvmfytwMiYL5=TQWhfpAjA@mail.gmail.com> (raw)
On Wed, Apr 11, 2018 at 1:24 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> It got sent from here as iso8859-1.
It's probably a good idea to just move away from Latin1 entirely, and
encourage people to just use utf-8.
But yes, Andrew's scripts clearly do a horrible job at looking at
email encoding, and that really should be fixed.
I worry less about silly copyright signs than about peoples actual
_names_, but we've certainly seen problems there too.
Linus
next reply other threads:[~2018-04-11 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 22:41 Linus Torvalds [this message]
2018-04-11 23:17 ` [PATCH] proc: fixup (c) sign Andrew Morton
2018-04-12 0:50 ` Al Viro
2018-04-12 17:14 Linus Torvalds
2018-04-12 19:50 ` Alexey Dobriyan
2018-04-12 20:16 ` Linus Torvalds
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='CA+55aFxrpn=GdgqgrczUdj-wndFdQvmfytwMiYL5=TQWhfpAjA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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).