Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [RFC/PATCH] mailinfo: do not treat ">From" lines as in-body headers

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:02:31

Jeff King [off-list ref] writes:
On Sat, Sep 13, 2014 at 05:55:49PM -0700, Junio C Hamano wrote:
quoted
On Sat, Sep 13, 2014 at 5:47 PM, Jeff King [off-list ref] wrote:
quoted
On Sat, Sep 13, 2014 at 10:57:14PM +0000, brian m. carlson wrote:
quoted
I wonder if git send-email should do what mutt does in this case, which
is use quoted-printable encoding and encode the first F as =46 (as well
as any equals signs as =3D).  It looks like mailinfo.c already is
capable of handling that, and that would avoid the entire issue.
That's not an unreasonable tactic. However, I think we'd still want to
do something with mailinfo on the receiving end, similar to the patch I
sent. We don't know that the sending side is necessarily send-email.
Hmm, isn't the ">" stuffing in front of a beginning-of-line "From " purely
a local matter of MUA that stores messages in (old-style) mbox format
where a line that begins with "From " is what defines the end of the
previous message?
Yes, it is[1].
quoted
Why should send-email do anything when it sends individual messages
separately out?
It does not need to, but the QP-transformation helps protect against
other, stupider software downstream.  And unlike From-quoting it is
actually well-specified and reversible.
Oh, I was only reacting to a phantom suggestion nobody made to add
">" on the sending side (which would not help anybody), but now I
re-read the thread with a larger screen I realize nobody made such a
suggestion.  Sorry for a noise.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help