Re: MIME problem when using git format-patch / git am

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Apr 27, 2010, 15:32 UTC
Message-ID: <20100427153250.GA14756@progeny.tock>
In-Reply-To: <alpine.DEB.2.00.1004260948070.22806@ds9.cixit.se>

Peter Krefting wrote:

> Jonathan Nieder:

Show 8 quoted lines

>> This leads to a question: what if one wants to include a word that
>> quotes to more than 75 characters?
>
> You just split it into two encoded words. The whitespace between the
> encoded words is there for syntactic reasons only, it is not
> included in the final result if both parts are encoded words (look
> at the "Examples" section of the RFC for some examples of how it
> works).

Thank you. He explains it before then, too; I should be reading more carefully.

I’ve been working through a full implementation of that RFC, but it seems that to support breaking words, Git would need to learn where the character boundaries are. Which means encodings would not be just opaque strings as far as git cares any more.

On the bright side, the only encoding I care about is UTF-8, and that one’s easy.

Jonathan