bug#24953: 25.1; Possible inefficiency in UTF-8

[Eli Zaretskii <eliz@gnu.org>]

> From: Eli Barzilay <eli@barzilay.org>
> Date: Sun, 11 Dec 2016 05:53:33 -0500
> Cc: 24953@debbugs.gnu.org
> 
> I still didn't get to try and see if I can get the git problem, but the
> problem seems to be moot for me: I use *both* Linux and Windows, a lot.
> I synchronize files between the two, and I work with Linux mounts on
> Windows.  In short, I have a ton of files that are UTF-8, so it makes
> sense to have it be my default on Windows too.  In the around-month-or-
> so which I used without it, I ran into several cases where the default
> character encoding was broken, and OTOH, in years of using an explicit
> UTF-8 I haven't had any problems...

Whatever you do, don't change the locale, because it will affect how
command-line arguments to subprocesses are encoded, which will bite
you some day.  If you need the text decoding/encoding to use UTF-8 by
default, use setq-default to change buffer-file-coding-system.