| commit | 05eda511b3baf7aa5ed1ed350e833aed6a44e6f1 | |
| author | Jeff King <peff@peff.net> | |
| Fri, 9 Nov 2012 17:50:29 +0000 (9 12:50 -0500) | ||
| committer | Jeff King <peff@peff.net> | |
| Fri, 9 Nov 2012 17:50:29 +0000 (9 12:50 -0500) | ||
| tree | 2a96521561bc9af22fd68bb93ed2c03c6c4fd934 | treesnapshot (tar.gz zip) |
| parent | 64b22a58949cd56c6ce586c1b9da1b1d32a2889e | commitdiff |
| parent | ce1459f740a591c63697ff6ff3c106123630539c | commitdiff |
Merge branch 'km/send-email-compose-encoding'
"git send-email --compose" can let the user create a non-ascii
cover letter message, but there was not a way to mark it with
appropriate content type before sending it out.
Further updates fix subject quoting.
* km/send-email-compose-encoding:
git-send-email: add rfc2047 quoting for "=?"
git-send-email: introduce quote_subject()
git-send-email: skip RFC2047 quoting for ASCII subjects
git-send-email: use compose-encoding for Subject
git-send-email: introduce compose-encoding
"git send-email --compose" can let the user create a non-ascii
cover letter message, but there was not a way to mark it with
appropriate content type before sending it out.
Further updates fix subject quoting.
* km/send-email-compose-encoding:
git-send-email: add rfc2047 quoting for "=?"
git-send-email: introduce quote_subject()
git-send-email: skip RFC2047 quoting for ASCII subjects
git-send-email: use compose-encoding for Subject
git-send-email: introduce compose-encoding