summaryrefslogtreecommitdiff
path: root/Documentation/git-send-email.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2012-11-09 12:50:29 -0500
committerLibravatar Jeff King <peff@peff.net>2012-11-09 12:50:29 -0500
commit05eda511b3baf7aa5ed1ed350e833aed6a44e6f1 (patch)
tree2a96521561bc9af22fd68bb93ed2c03c6c4fd934 /Documentation/git-send-email.txt
parentMerge branch 'js/format-2047' (diff)
parentgit-send-email: add rfc2047 quoting for "=?" (diff)
downloadtgif-05eda511b3baf7aa5ed1ed350e833aed6a44e6f1.tar.xz
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
Diffstat (limited to 'Documentation/git-send-email.txt')
-rw-r--r--Documentation/git-send-email.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 324117072d..eeb561cf14 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -126,6 +126,10 @@ The --to option must be repeated for each user you want on the to list.
+
Note that no attempts whatsoever are made to validate the encoding.
+--compose-encoding=<encoding>::
+ Specify encoding of compose message. Default is the value of the
+ 'sendemail.composeencoding'; if that is unspecified, UTF-8 is assumed.
+
Sending
~~~~~~~