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

Re: [RFC/PATCH 2/4] textconv: make diff_options accessible from blame

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:48:54

Junio C Hamano [off-list ref] writes:
Axel Bonnet [off-list ref] writes:
quoted
Diff_options specify whether conversion is activated or not. Blame needs
to access these options in order to concert files with external drivers

Signed-off-by: Diane Gasselin <redacted>
Signed-off-by: Clément Poulain <redacted>
Signed-off-by: Axel Bonnet <redacted>
The name of Clément is spelled correctly on the mail header while S-o-b
line is corrupt.
Actually, it's valid UTF-8, but there's no header specifying the
encoding in the email, therefore, the reader's default applies. My
mailer displays it correctly, but yours doesn't.
Perhaps you have recorded your commits in UTF-8 but allowed your MUA
to send in 8859-1?
The MUA seems to be git-send-email. According to the source (I didn't
find it in the doc), git-send-email looks at the patch's headers to
specify the encoding.

On my machine, the patch applies well, and if I re-export it using
format-patch, I do get the headers:

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

If I send myself the patch with git-send-email, I also get the headers
in the email (I tried from ensibm, which is the machine which sent the
patch serie). So, it doesn't look like a bug in git, but rather a
miss-use.

Axel, can you give us the exact command(s) you used to send the patch?

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help