From: Derek Fawcus <dfawcus@cisco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jay Soffian <jaysoffian@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] mailinfo: support rfc3676 (format=flowed) text/plain messages
Date: Sat, 16 Feb 2008 14:34:44 +0000 [thread overview]
Message-ID: <20080216143444.GU2456@cisco.com> (raw)
In-Reply-To: <7vr6fei1s4.fsf@gitster.siamese.dyndns.org>
On Fri, Feb 15, 2008 at 09:10:19AM -0800, Junio C Hamano wrote:
> I really do not like this.
>
> format=flowed instructs the receivers MUA that it is Ok to
> reflow the text when the message is presented to the user. That
> is exactly what we do _NOT_ want to happen to patches. Your
> implementation may cleanly salvage what the sender intended to
> send, but salvaging when applying the patch is too late.
>
> You review the patch, decide to apply or reject, and then
> finally apply. Unmangling of corrupt contents should be done
> before you review, not before you apply.
I have to agree that this is a bad idea - for the reasons stated,
and one additional:
There are MUA's which send 'format=fixed' email marked as 'format=flowed'.
At which point the receiving MUA performing the deflowing _will_ get
a corrupt patch.
I saw this recently wrt to internal company code reviews. We have
a variety of different MUAs in use on a variety of different OSs.
Some 'properly' implement format=flowed, some do not. Some always
send format=flowed for text, some can have it disabled to send
format=fixed. Despite what the RFCs say, some of them also QP
or base64 encode such flowed pieces of text. It is a nightmare.
However it seems thay all use fixed format for attachments, unfortunately
some them always tag those as application/octet-stream, so one cannot
automatically process them (in the absense of other clues).
I am able to work around some of these issues by configuing mutt to
do some guesses when it sees application/x-patch, or application/octet-stream
and a file with say as '.diff' extension.
But ultimately for some of these one is forced to contact the original
author and get access to the actual patch file on the filesystem.
While this can be done for a 'small' community, it is not something
that would work in the wider world.
So - format=flowed is simply unsuitable for fixed format text and should
not be used.
[Actually it rather turns out format=flowed is a bad idea all together,
you should see what it does to log files...]
DF
prev parent reply other threads:[~2008-02-16 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 2:21 [PATCH 1/2] mailinfo: support rfc3676 (format=flowed) text/plain messages Jay Soffian
2008-02-15 2:21 ` [PATCH 2/2] test mailinfo rfc3676 support Jay Soffian
2008-02-15 11:01 ` Johannes Schindelin
2008-02-15 16:44 ` Jay Soffian
2008-02-15 10:41 ` [PATCH 1/2] mailinfo: support rfc3676 (format=flowed) text/plain messages Johannes Schindelin
2008-02-15 16:35 ` Jay Soffian
2008-02-15 18:43 ` Jay Soffian
2008-02-16 2:30 ` Johannes Schindelin
2008-02-15 17:10 ` Junio C Hamano
2008-02-15 18:37 ` Jay Soffian
2008-02-16 6:57 ` Junio C Hamano
2008-02-16 7:43 ` Jay Soffian
2008-02-16 9:59 ` Junio C Hamano
2008-02-16 14:34 ` Derek Fawcus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080216143444.GU2456@cisco.com \
--to=dfawcus@cisco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).