Re: [PATCH 1/2] mailinfo: support rfc3676 (format=flowed) text/plain messages

From: Jay Soffian <jaysoffian@gmail.com>
Date: Feb 16, 2008, 07:43 UTC
Message-ID: <76718490802152343g6a987c8ay80493187d0a3ccba@mail.gmail.com>
In-Reply-To: <7vodahcrrl.fsf@gitster.siamese.dyndns.org>

On Feb 16, 2008 1:57 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 5 quoted lines

> But format=flowed is different.  It loses information.  Not just
> one space at the end of the original line, but if you have very
> long line that has more than one spaces at an unfortunate place,
> the sending MUA can cut the line there and leave a single
> trailing space for the receiving end to reflow.

Well, according to the RFC, that shouldn't be the case. The only lost information should be trailing whitespace. Embedded whitespace should not be altered.

> RFC3676 may be a good text communication medium.  It is just not
> suitable for patch transfer.  Just don't use it.

Would you consider making this configurable. Something like:

applymail.allowed_flowed = true/false/warn

If you're completely opposed though, we should modify git-am (and/or mailinfo) to reject format=flowed messages entirely, no?

j.