From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] treewide: convert ISO_8859-1 text comments to utf-8
Date: Tue, 24 Jul 2018 14:00:10 -0700 [thread overview]
Message-ID: <20180724140010.e24a9964fd340afe2d98a994@linux-foundation.org> (raw)
In-Reply-To: <20180724111600.4158975-1-arnd@arndb.de>
On Tue, 24 Jul 2018 13:13:25 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
> Almost all files in the kernel are either plain text or UTF-8
> encoded. A couple however are ISO_8859-1, usually just a few
> characters in a C comments, for historic reasons.
>
> This converts them all to UTF-8 for consistency.
Was "consistency" the only rationale? The discussion is now outside my
memory horizon but I thought there were other reasons.
Will we be getting a checkpatch rule to keep things this way?
next prev parent reply other threads:[~2018-07-24 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 11:13 [PATCH 1/4] treewide: convert ISO_8859-1 text comments to utf-8 Arnd Bergmann
2018-07-24 15:33 ` Simon Horman
2018-07-24 21:00 ` Andrew Morton [this message]
2018-07-24 21:02 ` Randy Dunlap
2018-07-25 0:13 ` Joe Perches
2018-07-25 0:55 ` Andrew Morton
2018-07-25 13:12 ` Arnd Bergmann
2018-07-25 15:33 ` Joe Perches
2018-07-24 21:04 ` Jonathan Cameron
2018-07-25 4:20 ` Michael Ellerman
2018-07-31 21:49 ` Rob Herring
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=20180724140010.e24a9964fd340afe2d98a994@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.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).