From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Joe Perches <joe@perches.com>,
Samuel Ortiz <sameo@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Jonathan Cameron <jic23@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-iio@vger.kernel.org, linux-pm@vger.kernel.org,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [PATCH 1/4] treewide: convert ISO_8859-1 text comments to utf-8
Date: Tue, 24 Jul 2018 14:02:30 -0700 [thread overview]
Message-ID: <d5cf9579-5d61-dafc-5109-b86bfca07dce@infradead.org> (raw)
In-Reply-To: <20180724140010.e24a9964fd340afe2d98a994@linux-foundation.org>
On 07/24/2018 02:00 PM, Andrew Morton wrote:
> 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.
kconfig tools prefer ASCII or utf-8.
email tools probably likewise.
user sanity?
> Will we be getting a checkpatch rule to keep things this way?
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: rdunlap@infradead.org (Randy Dunlap)
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:02:30 -0700 [thread overview]
Message-ID: <d5cf9579-5d61-dafc-5109-b86bfca07dce@infradead.org> (raw)
In-Reply-To: <20180724140010.e24a9964fd340afe2d98a994@linux-foundation.org>
On 07/24/2018 02:00 PM, Andrew Morton wrote:
> 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.
kconfig tools prefer ASCII or utf-8.
email tools probably likewise.
user sanity?
> Will we be getting a checkpatch rule to keep things this way?
--
~Randy
next prev parent reply other threads:[~2018-07-24 22:11 UTC|newest]
Thread overview: 36+ 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 11:13 ` Arnd Bergmann
2018-07-24 11:13 ` Arnd Bergmann
2018-07-24 11:13 ` [PATCH 2/4] s390: ebcdic: convert comments to UTF-8 Arnd Bergmann
2018-07-24 11:13 ` [PATCH 3/4] lib/fonts: convert comments to utf-8 Arnd Bergmann
2018-07-24 11:13 ` [PATCH 4/4] staging: rtl8188eu/rtl8723bs: fix character encoding Arnd Bergmann
2018-07-24 11:53 ` Greg Kroah-Hartman
2018-07-24 11:55 ` Greg Kroah-Hartman
2018-07-24 15:33 ` [PATCH 1/4] treewide: convert ISO_8859-1 text comments to utf-8 Simon Horman
2018-07-24 15:33 ` Simon Horman
2018-07-24 15:33 ` Simon Horman
2018-07-24 21:00 ` Andrew Morton
2018-07-24 21:00 ` Andrew Morton
2018-07-24 21:02 ` Randy Dunlap [this message]
2018-07-24 21:02 ` Randy Dunlap
2018-07-25 0:13 ` Joe Perches
2018-07-25 0:13 ` Joe Perches
2018-07-25 0:55 ` Andrew Morton
2018-07-25 0:55 ` Andrew Morton
2018-07-25 13:12 ` Arnd Bergmann
2018-07-25 13:12 ` Arnd Bergmann
2018-07-25 13:12 ` Arnd Bergmann
2018-07-25 15:33 ` Joe Perches
2018-07-25 15:33 ` Joe Perches
2018-07-25 15:33 ` Joe Perches
2018-07-25 15:33 ` Joe Perches
2018-07-25 15:33 ` Joe Perches
2018-07-24 21:04 ` Jonathan Cameron
2018-07-24 21:04 ` Jonathan Cameron
2018-07-24 21:04 ` Jonathan Cameron
2018-07-25 4:20 ` Michael Ellerman
2018-07-25 4:20 ` Michael Ellerman
2018-07-25 4:20 ` Michael Ellerman
2018-07-25 4:20 ` Michael Ellerman
2018-07-31 21:49 ` Rob Herring
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=d5cf9579-5d61-dafc-5109-b86bfca07dce@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvs-devel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.