Re: `git-send-email' doesn't specify `Content-Type'

From: Jeff King <peff@peff.net>
Date: Nov 11, 2007, 08:51 UTC
Message-ID: <20071111085120.GD30299@sigill.intra.peff.net>
In-Reply-To: <20071111084515.GB18021@bulgaria>

On Sun, Nov 11, 2007 at 12:45:15AM -0800, Brian Swetland wrote:

> > > What happens if the metadata has utf8 content and the patch itself has 
> > > some *other* non-ascii encoding (some iso-latin variant perhaps).

[...]

Show 7 quoted lines

> > 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.
> 
> That seems potentially bad in that the transport (mailed patches) could
> be altering the contents of the patch.  Or is this process reversed when 
> the patch is finally applied?

My answer was for "how do you stick two things with different encoding in the same mail" (which applies to the name + commit message situation). However, we don't actually _have_ an encoding for the patch data. We just assume that it matches the metadata.

-Peff