From: Laurent Vivier <laurent@vivier.eu>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Aleksandar Markovic <amarkovic@wavecomp.com>
Subject: Re: [Qemu-devel] [PATCH v5-resend 2/2] mips_fulong2e: Add on-board graphics chip
Date: Fri, 8 Mar 2019 17:40:51 +0100 [thread overview]
Message-ID: <c4b00c71-a429-a48f-b861-3cedc63da2d9@vivier.eu> (raw)
In-Reply-To: <7005c46c-e22a-a4ba-9c4d-30cf0fadb5f5@redhat.com>
Le 08/03/2019 à 17:35, Philippe Mathieu-Daudé a écrit :
> On 3/8/19 5:22 PM, BALATON Zoltan wrote:
>> On Fri, 8 Mar 2019, Gerd Hoffmann wrote:
>>> On Thu, Mar 07, 2019 at 01:32:41AM +0100, Philippe Mathieu-Daudé wrote:
>>>> On 3/6/19 9:05 PM, BALATON Zoltan wrote:
>>>>> Add (partial) emulation of the on-board GPU of the machine. This
>>>>> allows the PMON2000 firmware to run and should also work with Linux
>>>>> console but probably not with X yet.
>>>>>
>>>>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>>>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>>> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>>
>>>> Mojibaked again :(
>>>
>>> Mail was sent without Content-Type: header. Both mutt and "git am" on
>>> my machine assume utf-8 and everything looks fine. I guess your mail
>>> client assumes something else ...
>>
>> So it came out good at the end but that depends on what maintainer's
>> config does by default it seems.
>>
>>> "git send-email" should send the patches with correct headers, it even
>>> asks for the charset it should use in case it finds non-ascii
>>> characters. So BALATON, could you check your mail client config, or
>>> switch over to "git send-email" for submitting patches?
>>
>> I'm sending what git format-patch is generating and that does not add
>> content type header by default. Is there a config option to enable that?
>> I can't use git send-email because I'm sending from different machine
>> than I use git on.
>
> On another thread Laurent Vivier found it is a copy/paste problem
> between an email client and an editor (IIUC):
> https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg03669.html
>
> Laurent, if you understood what's wrong, can you add en entry in the
> wiki so we can refer contributors to it?
No sure. My guess is a cut'n'paste between two windows with different
charsets doesn't work because the buffer keeps the char encoding of the
first window and put them as raw binaries in the second one, so it
encodes something else.
Thanks,
Laurent
next prev parent reply other threads:[~2019-03-08 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 20:05 [Qemu-devel] [PATCH v5-resend 0/2] Basic ATI VGA emulation BALATON Zoltan
2019-03-06 20:05 ` [Qemu-devel] [PATCH v5-resend 1/2] hw/display: Add basic " BALATON Zoltan
2019-03-06 20:05 ` [Qemu-devel] [PATCH v5-resend 2/2] mips_fulong2e: Add on-board graphics chip BALATON Zoltan
2019-03-07 0:32 ` Philippe Mathieu-Daudé
2019-03-07 0:38 ` BALATON Zoltan
2019-03-07 13:38 ` Aleksandar Markovic
2019-03-08 7:32 ` Gerd Hoffmann
2019-03-08 16:22 ` BALATON Zoltan
2019-03-08 16:35 ` Philippe Mathieu-Daudé
2019-03-08 16:40 ` Laurent Vivier [this message]
2019-03-11 6:38 ` Gerd Hoffmann
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=c4b00c71-a429-a48f-b861-3cedc63da2d9@vivier.eu \
--to=laurent@vivier.eu \
--cc=amarkovic@wavecomp.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).