From: David Woodhouse <dwmw2@infradead.org>
To: Bertrand Jacquin <beber.mailing@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Features ask for git-send-email
Date: Tue, 02 May 2006 13:36:57 +0100 [thread overview]
Message-ID: <1146573417.14059.21.camel@pmac.infradead.org> (raw)
In-Reply-To: <4fb292fa0604290630r19edd7ejf88642e33b350d1d@mail.gmail.com>
On Sat, 2006-04-29 at 15:30 +0200, Bertrand Jacquin wrote:
> Could it be possible to add a features in git-send-email.perl to
> accept a differrent charset as iso-8859-1 ? I would like to send
> fr_FR.utf8 mail as I use git to manager a latex files tree which are
> written in utf8.
>
> Any objection ?
Seems reasonable. I think we just forgot to include the Content-Type:
header. This fixes it...
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
diff --git a/git-send-email.perl b/git-send-email.perl
index ecfa347..1df75f5 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -37,7 +37,7 @@ # Constants (essentially)
my $compose_filename = ".msg.$$";
# Variables we fill in automatically, or via prompting:
-my (@to,@cc,@initial_cc,$initial_reply_to,$initial_subject,@files,$from,$compose,$time);
+my (@to,@cc,@initial_cc,$initial_reply_to,$initial_subject,@files,$from,$compose,$time,$charset);
# Behavior modification variables
my ($chain_reply_to, $smtp_server, $quiet, $suppress_from, $no_signed_off_cc) = (1, "localhost", 0, 0, 0);
@@ -58,6 +58,7 @@ my $rc = GetOptions("from=s" => \$from,
"chain-reply-to!" => \$chain_reply_to,
"smtp-server=s" => \$smtp_server,
"compose" => \$compose,
+ "charset=s" => \$charset,
"quiet" => \$quiet,
"suppress-from" => \$suppress_from,
"no-signed-off-cc|no-signed-off-by-cc" => \$no_signed_off_cc,
@@ -135,6 +136,10 @@ if (!defined $smtp_server) {
$smtp_server = "localhost";
}
+if (!defined $charset) {
+ $charset = "UTF-8";
+}
+
if ($compose) {
# Note that this does not need to be secure, but we will make a small
# effort to have it be unique
@@ -214,6 +219,9 @@ Options:
--cc Specify an initial "Cc:" list for the entire series
of emails.
+ --charset Specify a character set, if legacy character sets are
+ used in change logs instead of UTF-8.
+
--compose Use \$EDITOR to edit an introductory message for the
patch series.
@@ -299,6 +307,7 @@ Subject: $subject
Reply-To: $from
Date: $date
Message-Id: $message_id
+Content-Type: text/plain; charset=$charset
X-Mailer: git-send-email @@GIT_VERSION@@
";
$header .= "In-Reply-To: $reply_to\n" if $reply_to;
--
dwmw2
next prev parent reply other threads:[~2006-05-02 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 13:30 Features ask for git-send-email Bertrand Jacquin
2006-05-02 12:36 ` David Woodhouse [this message]
2006-05-02 12:53 ` Jakub Narebski
2006-05-02 14:14 ` David Woodhouse
2006-05-02 15:35 ` Jakub Narebski
2006-05-02 22:46 ` Bertrand Jacquin
2006-05-02 23:33 ` David Woodhouse
2006-05-02 23:51 ` Bertrand Jacquin
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=1146573417.14059.21.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=beber.mailing@gmail.com \
--cc=git@vger.kernel.org \
/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).