From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Hannes Reinecke" <hare@suse.com>,
qemu-block@nongnu.org, qemu-trivial@nongnu.org,
"Jason Wang" <jasowang@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Chubb" <peter.chubb@nicta.com.au>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-arm@nongnu.org, "Kővágó, Zoltán" <dirty.ice.hu@gmail.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH 0/6] Fix more GCC9 -O3 warnings
Date: Thu, 23 Jan 2020 18:55:08 +0100 [thread overview]
Message-ID: <47e28e48-362a-39ea-ee58-9bbe7d222394@redhat.com> (raw)
In-Reply-To: <87blquza17.fsf@linaro.org>
On 1/23/20 12:28 PM, Alex Bennée wrote:
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>
>> On 12/17/19 6:32 PM, Philippe Mathieu-Daudé wrote:
>>> Fix some trivial warnings when building with -O3.
>>> Philippe Mathieu-Daudé (6):
>>> audio/audio: Add missing fall through comment
>>> hw/display/tcx: Add missing fall through comments
>>> hw/net/imx_fec: Rewrite fall through comments
>>> hw/timer/aspeed_timer: Add a fall through comment
>>> hw/scsi/megasas: Silent GCC9 duplicated-cond warning
>>> qemu-io-cmds: Silent GCC9 format-overflow warning
>>
>> Sorry, this series failed because I used this tag in the first patch:
>>
>> Cc: Kővágó, Zoltán <dirty.ice.hu@gmail.com>
>>
>> Then git-send-email was happy with --dry-run, but then failed:
>> (body) Adding cc: Kővágó, Zoltán <dirty.ice.hu@gmail.com> from line
>> 'Cc: Kővágó, Zoltán <dirty.ice.hu@gmail.com>'
>> 5.1.1 <K v g >: Recipient address rejected: User unknown in local
>> recipient table
>>
>> Note to self, enclose utf-8 names, as:
>> Cc: "Kővágó, Zoltán" <dirty.ice.hu@gmail.com>
>
> I never have to with my tags:
>
> Cc: Alex Bennée <alex.bennee@linaro.org>
>
> Is it possible to be more even utf-8? Sounds like a bug in the git tools
> to me.
The problem is the comma.
What do you mean by "more UTF-8"?
next prev parent reply other threads:[~2020-01-23 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 17:32 [PATCH 0/6] Fix more GCC9 -O3 warnings Philippe Mathieu-Daudé
2019-12-17 17:39 ` Philippe Mathieu-Daudé
2020-01-23 11:28 ` Alex Bennée
2020-01-23 17:55 ` Philippe Mathieu-Daudé [this message]
2020-01-23 18:26 ` Alex Bennée
2019-12-17 21:49 ` Chubb, Peter (Data61, Kensington NSW)
2019-12-18 6:05 ` Markus Armbruster
2020-01-18 19:24 ` Paolo Bonzini
2020-01-20 19:02 ` Philippe Mathieu-Daudé
2020-01-21 10:49 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2019-12-17 17:34 Philippe Mathieu-Daudé
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=47e28e48-362a-39ea-ee58-9bbe7d222394@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=dirty.ice.hu@gmail.com \
--cc=fam@euphon.net \
--cc=hare@suse.com \
--cc=jasowang@redhat.com \
--cc=joel@jms.id.au \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.chubb@nicta.com.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
/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).