David Kastrup <dak@xxxxxxx> writes: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> 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. - 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
