From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: anthony@redhat.com, qemu-devel@nongnu.org,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL 00/12] migration queue
Date: Thu, 27 Jun 2013 15:57:58 -0400 [thread overview]
Message-ID: <51CC9946.10202@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFEAcA_P24jsuLZz+CB8VAqDKZkEnya1F_OM8Kde5SGtnyVjQw@mail.gmail.com>
On 06/27/2013 03:20 PM, Peter Maydell wrote:
> On 27 June 2013 11:37, Juan Quintela <quintela@redhat.com> wrote:
>> Anthony, please pull.
>>
>> - improve error message (Alon)
>> - Make zero pages to work again (Peter Lieven)
>> - First 10 patches of RDMA support
> Hi; could you adjust your pullrequest scripts to retransmit
> the patches as followup emails to the pullreq mail, please?
> It makes it easier to follow up when patches within a merge
> turn out to have issues.
>
> (cf http://wiki.qemu.org/Contribute/SubmitAPullRequest
> and previous on-list discussion.)
>
> thanks
> -- PMM
>
Ooops..... forgot to move the #endif in the patch - I never tried any of
the other compilation targets before = )
Will send a fix ASAP in the next patch series.
- Michael
next prev parent reply other threads:[~2013-06-27 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 10:37 [Qemu-devel] [PULL 00/12] migration queue Juan Quintela
2013-06-27 18:56 ` Peter Maydell
2013-06-27 19:20 ` Peter Maydell
2013-06-27 19:57 ` Michael R. Hines [this message]
2013-06-28 5:27 ` Juan Quintela
2013-06-27 22:29 ` Peter Maydell
2013-06-28 5:32 ` Juan Quintela
2013-06-28 14:20 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 12:53 [Qemu-devel] [PULL 00/12] Migration queue Juan Quintela
2019-09-12 13:49 [Qemu-devel] [PULL 00/12] migration queue Dr. David Alan Gilbert (git)
2019-09-13 14:44 ` 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=51CC9946.10202@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=anthony@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.