Re: git am and CRLF files

From: Daniele Segato <daniele.bilug@gmail.com>
Date: Nov 30, 2009, 12:06 UTC
Message-ID: <9accb4400911300406l592306c8t889c28ba7b48674b@mail.gmail.com>
In-Reply-To: <40aa078e0911160343k41393197s56d26576bcbfbe90@mail.gmail.com>

On Mon, Nov 16, 2009 at 12:43 PM, Erik Faye-Lund <kusmabite@googlemail.com> wrote:

Show 13 quoted lines

> According to RFC 5322, email messages use CRLF as the
> newline-sequence. In order to be able to distinguish between CRLF and
> LF in an e-mail patch, the message needs to be use some
> transfer-encoding that preserves newline style (like base64).
>
> Perhaps this would be better fixed by having format-patch (or prehaps
> the MUA ?) base64-encode the message body if the file contains
> non-LF-newlines, and normalizing CRLF to LF before transport-decoding?
> Or does some MUAs transport-decode before storing the message to disk?
>
> I realize this might make it a bit tricky to review patches that
> contains CRLF-newlines before mailing them out, but perhaps inspecting
> the format-patch output is the wrong place to do this?

why don't adding that information in the mail header? or may be made format-patch create a "comment line" with that information?

if that line is missing it could keep the default behavior (what it did until now)