From: bonneta <bonneta@ensimag.fr>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: <git@vger.kernel.org>
Subject: Re: [RFC/PATCH 2/4] textconv: make diff_options accessible from blame
Date: Fri, 04 Jun 2010 12:21:07 +0200 [thread overview]
Message-ID: <57f94007bc6d4f34d1929a005110073f@ensimag.fr> (raw)
In-Reply-To: <vpqy6evut1o.fsf@bauges.imag.fr>
On Fri, 04 Jun 2010 09:59:47 +0200, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Axel Bonnet <axel.bonnet@ensimag.imag.fr> writes:
>>
>>> 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 <diane.gasselin@ensimag.imag.fr>
>>> Signed-off-by: Clément Poulain <clement.poulain@ensimag.imag.fr>
>>> Signed-off-by: Axel Bonnet <axel.bonnet@ensimag.imag.fr>
>>
>> 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?
I made the patch with "git send-email --cover --annotate", and then edited
the messages with vim.
I added the S-o-b lines by copy-pasting them from the test mail I
had send to Matthieu (from thunderbird). I saw there was a problem of
encoding with the "é" of
Clément, so I modified it.
I think I should have written the S-o-b lines directly in vim.
next prev parent reply other threads:[~2010-06-04 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 10:47 [RFC/PATCH 0/4] textconv support for blame Axel Bonnet
2010-06-03 10:47 ` [RFC/PATCH 1/4] textconv: make the API public Axel Bonnet
2010-06-03 10:47 ` [RFC/PATCH 2/4] textconv: make diff_options accessible from blame Axel Bonnet
2010-06-03 10:47 ` [RFC/PATCH 3/4] textconv: support for blame Axel Bonnet
2010-06-03 10:47 ` [RFC/PATCH 4/4] t/t8006: test textconv " Axel Bonnet
2010-06-03 15:44 ` Johannes Sixt
2010-06-04 8:55 ` Diane Gasselin
2010-06-04 9:45 ` Matthieu Moy
2010-06-04 8:49 ` Matthieu Moy
2010-06-04 6:00 ` [RFC/PATCH 3/4] textconv: " Junio C Hamano
2010-06-04 10:34 ` Diane Gasselin
2010-06-06 21:51 ` Jeff King
2010-06-04 5:48 ` [RFC/PATCH 2/4] textconv: make diff_options accessible from blame Junio C Hamano
2010-06-04 7:59 ` Matthieu Moy
2010-06-04 10:21 ` bonneta [this message]
2010-06-04 17:23 ` Matthieu Moy
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=57f94007bc6d4f34d1929a005110073f@ensimag.fr \
--to=bonneta@ensimag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/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).