diff options
author | Emma Brooks <me@pluvano.com> | 2020-04-08 04:31:38 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-04-07 22:37:18 -0700 |
commit | 19d097e3d73b4d3635bbe0e8735b2f059d59f29a (patch) | |
tree | 46a74286c5a82ccc9805a758ba449d07ad8a767f /t/t4211/sha1/expect.vanishes-early | |
parent | Merge branch 'ds/default-pack-use-sparse-to-true' (diff) | |
download | tgif-19d097e3d73b4d3635bbe0e8735b2f059d59f29a.tar.xz |
format-patch: teach --no-encode-email-headers
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.
Add --[no-]encode-email-headers and format.encodeEmailHeaders to let the
user control this behavior.
Signed-off-by: Emma Brooks <me@pluvano.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4211/sha1/expect.vanishes-early')
0 files changed, 0 insertions, 0 deletions