Re: [PATCH] format-patch: teach --no-encode-headers

From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Emma Brooks <me@pluvano.com>
Cc: git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
	Eric Sunshine <sunshine@sunshineco.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] format-patch: teach --no-encode-headers
Date: Mon, 6 Apr 2020 03:04:44 +0000	[thread overview]
Message-ID: <20200406030444.GG6369@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20200405231109.8249-1-me@pluvano.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On 2020-04-05 at 23:11:09, Emma Brooks wrote:
> When commit subjects or authors have non-ASCII characters, git
> format-patch Q-encodes them so they can be safely sent over email.
> However, if the patch transfer method is something other than email (web
> review tools, sneakernet), this only serves to make the patch metadata
> harder to read without first applying it (unless you can decode RFC 2047
> in your head). git am as well as some email software supports
> non-Q-encoded mail as described in RFC 6531.

Do we always output UTF-8 in this case, or do we sometimes output other
encodings if the user has specified one for the commit message?  Do we
know how git send-email handles such a message if it receives one?

I know it isn't your intention to work with git send-email in this
patch, but it would be nice to know whether there's additional value in
someone sending a followup patch to make git send-email use SMTPUTF8 if
that's necessary.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]