Daniele Segato escribió: > On Mon, Nov 16, 2009 at 12:43 PM, Erik Faye-Lund > <kusmabite@xxxxxxxxxxxxxx> wrote: >> 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) > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html It would make more sense to simply use MIME attachments... -- Ismael Luceno
Attachment:
signature.asc
Description: OpenPGP digital signature