From: Jeff King <peff@peff.net>
To: Brian Swetland <swetland@google.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Ludovic Courtès" <ludo@chbouib.org>,
git@vger.kernel.org
Subject: Re: `git-send-email' doesn't specify `Content-Type'
Date: Sun, 11 Nov 2007 03:41:17 -0500 [thread overview]
Message-ID: <20071111084117.GC30299@sigill.intra.peff.net> (raw)
In-Reply-To: <20071111083915.GA18021@bulgaria>
On Sun, Nov 11, 2007 at 12:39:15AM -0800, Brian Swetland wrote:
> This issue with the encoding of the author got me thinking...
>
> What happens if the metadata has utf8 content and the patch itself has
> some *other* non-ascii encoding (some iso-latin variant perhaps).
>
> Is there any way to deal with that situation sanely other than indicate
> that it's 8bit content and not specify an encoding? Is that what
> happens currently?
The body has to be in one encoding, so at the time that you know both
encodings, you have to pick one and convert the data from the discarded
encoding into the used encoding.
-Peff
next prev parent reply other threads:[~2007-11-11 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 0:14 `git-send-email' doesn't specify `Content-Type' Ludovic Courtès
2007-11-10 0:52 ` Johannes Schindelin
2007-11-10 10:14 ` Brian Swetland
2007-11-10 12:25 ` Björn Steinbrink
2007-11-10 12:35 ` Brian Swetland
2007-11-10 12:51 ` Björn Steinbrink
2007-11-11 8:32 ` Jeff King
2007-11-11 8:35 ` Jeff King
2007-11-11 8:39 ` Brian Swetland
2007-11-11 8:41 ` Jeff King [this message]
2007-11-11 8:45 ` Brian Swetland
2007-11-11 8:51 ` Jeff King
2007-11-11 8:56 ` Jeff King
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=20071111084117.GC30299@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=B.Steinbrink@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ludo@chbouib.org \
--cc=swetland@google.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).