Thread (2 messages) 2 messages, 2 authors, 2016-06-15

Re: Stupid quoting...

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:18

David Kastrup [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
quoted
If I were to create a patch between two versions of such a file, the
diff header would show the pathname encoded in one, and the changed
contents would ben shown in another.  As long as you treat "git
diff" output as binary blob, that would work just fine, but when you
have to transmit such a diff in e-mail as an in-line patch, you
would have troubles.
ASCII-armoring of what amounts to binary files is the task of the mail
software.  Also working with encodings.  Escaping characters in the
diff headers but not in the file contents is not going to achieve
anything useful, anyway.
You misunderstood me.  The issue is not about transmitting
without corruption.  Armoring would make it impossible to
COMMENTING on the patch INLINE.

And that is where the pathname quoting git diff does originally
comes from.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help