[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180724140010.e24a9964fd340afe2d98a994@linux-foundation.org>
Date: Tue, 24 Jul 2018 14:00:10 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Joe Perches <joe@...ches.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Michael Ellerman <mpe@...erman.id.au>,
Jonathan Cameron <jic23@...nel.org>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-crypto@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-iio@...r.kernel.org,
linux-pm@...r.kernel.org, lvs-devel@...r.kernel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org
Subject: Re: [PATCH 1/4] treewide: convert ISO_8859-1 text comments to utf-8
On Tue, 24 Jul 2018 13:13:25 +0200 Arnd Bergmann <arnd@...db.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?
Powered by blists - more mailing lists