All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
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 13:16:06 -0700	[thread overview]
Message-ID: <CA+55aFwJSQehU1tuSKJAXnro4vc_hU5W1-qL6XUO8BBpkK06rg@mail.gmail.com> (raw)
In-Reply-To: <20180412195024.GA17810@avx2>

On Thu, Apr 12, 2018 at 12:50 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> I've checked earlier mails, mutt has been "guessing" outgoing encoding
> by default. Let's try again.

I think it still does. This email came with

    Content-Type: text/plain; charset=us-ascii

which is what I'd expect if Mutt has a "use the least complex charset
that can fit the message".

If you look at my emails, you should see

    Content-Type: text/plain; charset="UTF-8"

even for an email like this, that only has 7-bit ascii.

I'm not a Mutt user, so I don't know what the magic is for "just force
utf-8 when sending".

For alpine, it's

    posting-character-set=UTF-8

in the .pinerc file.

For gmail there used to be an "outgoing message encoding" setting, but
it seems to have been removed (and now utf-8 is always on).

             Linus

  reply	other threads:[~2018-04-12 20:16 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
2018-04-12 20:16   ` Linus Torvalds [this message]
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=CA+55aFwJSQehU1tuSKJAXnro4vc_hU5W1-qL6XUO8BBpkK06rg@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 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.