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 --]
next prev parent reply other threads:[~2020-04-06 3:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:11 [PATCH] format-patch: teach --no-encode-headers Emma Brooks
2020-04-06 3:04 ` brian m. carlson [this message]
2020-04-06 13:30 ` Jeff King
2020-04-06 15:17 ` brian m. carlson
2020-04-06 15:30 ` Jeff King
2020-04-06 3:29 ` Junio C Hamano
2020-04-07 3:46 ` Emma Brooks
2020-04-07 19:37 ` Junio C Hamano
2020-04-07 20:31 ` Jeff King
2020-04-07 22:20 ` Junio C Hamano
2020-04-08 4:08 ` Emma Brooks
2020-04-07 5:17 ` [PATCH v2] format-patch: teach --no-q-encode-headers Emma Brooks
2020-04-07 7:40 ` Danh Doan
2020-04-08 3:57 ` Emma Brooks
2020-04-08 4:31 ` [PATCH v3] format-patch: teach --no-encode-email-headers Emma Brooks
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=20200406030444.GG6369@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=me@pluvano.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
/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).