From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
Edgar Iglesias <edgar.iglesias@xilinx.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the
Date: Thu, 7 Sep 2017 19:08:26 +0100 [thread overview]
Message-ID: <CAFEAcA8e9c_kB8b-LEWNGDPoyPfrEHp4_z9cCK70gPzcaV4Wrg@mail.gmail.com> (raw)
In-Reply-To: <57594b14-dbe1-9542-6bdb-eb0b5dc1314a@linaro.org>
On 7 September 2017 at 19:06, Richard Henderson
<richard.henderson@linaro.org> wrote:
> On 09/07/2017 09:48 AM, Alistair Francis wrote:
>> Hmmm... I'm not sure how to look into this then, as I can see the
>> patches going through to my personal email address, so it's hard to
>> place the blame on the Xilinx mail server.
>>
>> Do you want me to try sending out patches 1 and 3 again?
>
> I had this problem with one of my patch sets earlier this year.
> In the end it seemed easier to post a link to a public git tree.
Being on the direct cc list I get all the patches anyway, so
it's mostly an issue for (1) review by other people not directly
cc'd and (2) the automated tools (I can apply stuff by hand from
direct email but it's a pain as I have to manually save and
then git am every email in the set).
thanks
-- PMM
next prev parent reply other threads:[~2017-09-07 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:34 [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the Alistair Francis
2017-08-31 23:34 ` [Qemu-devel] [PATCH v2 4/5] xlnx-zcu102: Add a machine level virtualization property Alistair Francis
2017-08-31 23:34 ` [Qemu-devel] [PATCH v2 5/5] xlnx-zcu102: Mark the EP108 machine as deprecated Alistair Francis
2017-09-07 12:51 ` [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the Peter Maydell
2017-09-07 16:01 ` Alistair Francis
2017-09-07 16:29 ` Alistair Francis
2017-09-07 16:33 ` Peter Maydell
2017-09-07 16:48 ` Alistair Francis
2017-09-07 18:06 ` Richard Henderson
2017-09-07 18:08 ` Peter Maydell [this message]
2017-09-07 18:13 ` Alistair Francis
2017-09-07 15:57 ` [Qemu-devel] [PATCH Resend v2 2/5] xlnx-zcu102: Manually create the machines Alistair Francis
2017-09-07 21:35 ` [Qemu-devel] [PATCH Resend v2 0/5] Expose the secure and virt properties to the Edgar E. Iglesias
2017-09-07 21:44 ` Alistair Francis
2017-09-14 12:30 ` Peter Maydell
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=CAFEAcA8e9c_kB8b-LEWNGDPoyPfrEHp4_z9cCK70gPzcaV4Wrg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).