From: Alexey Dobriyan <adobriyan@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] proc: fixup (c) sign
Date: Thu, 12 Apr 2018 22:50:24 +0300 [thread overview]
Message-ID: <20180412195024.GA17810@avx2> (raw)
In-Reply-To: <CA+55aFxj+NjW3M0Sv_-DRAD6vJ=HsPCQMtHn88me9uEEnJmAPw@mail.gmail.com>
On Thu, Apr 12, 2018 at 10:14:35AM -0700, Linus Torvalds wrote:
> On Wed, Apr 11, 2018 at 1:19 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > Andrew's scripts butchered it :-(
>
> Oh, it's not just Andrew.
>
> Git will fix up commit messages etc, but the actual *patch* will be
> considered just "data". So if you send me Latin1 (like you did), I get
> a patch with Latin1.
>
> Please just fix your broken mail environment, and move to the current
> century. Use a real utf-8 locale.
>
> You seem to be using Mutt. Afaik, that should automatically honor your
> locale, and use utf-8,
>
> But maybe you have it trying to send in Latin1 by default if that
> works. Just do something like
>
> set file_charset="utf-8:iso-8859-1"
>
> to make utf-8 the preferred format.
I've checked earlier mails, mutt has been "guessing" outgoing encoding
by default. Let's try again.
next prev parent reply other threads:[~2018-04-12 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 17:14 [PATCH] proc: fixup (c) sign Linus Torvalds
2018-04-12 19:50 ` Alexey Dobriyan [this message]
2018-04-12 20:16 ` Linus Torvalds
2018-04-12 19:53 ` [PATCH v3] proc: fixup copyright sign Alexey Dobriyan
2018-04-12 20:31 ` [PATCH v4] " Alexey Dobriyan
2018-04-12 20:34 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 22:41 [PATCH] proc: fixup (c) sign Linus Torvalds
2018-04-11 23:17 ` Andrew Morton
2018-04-12 0:50 ` Al Viro
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=20180412195024.GA17810@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).