From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v4 00/30] QAPI patches for 2018-03-01
Date: Mon, 5 Mar 2018 12:15:52 +0000 [thread overview]
Message-ID: <CAFEAcA-WgS9nLC3iEQXi3p5Lhb1EDK-UEpty0ahgiG9ooPtLQQ@mail.gmail.com> (raw)
In-Reply-To: <20180302195143.31678-1-eblake@redhat.com>
On 2 March 2018 at 19:51, Eric Blake <eblake@redhat.com> wrote:
> The following changes since commit 136c67e07869227b21b3f627316e03679ce7b738:
>
> Merge remote-tracking branch 'remotes/bkoppelmann/tags/pull-tricore-2018-03-02' into staging (2018-03-02 16:56:20 +0000)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/ericb.git tags/pull-qapi-2018-03-01-v4
>
> for you to fetch changes up to 418b1d0ae3a2cc992659f626a2a3f11944e0b259:
>
> qapi: Don't create useless directory qapi-generated (2018-03-02 13:48:26 -0600)
>
> v4: another attempt at silencing OSX warnings on empty .o [Peter]
> (sending just the changed patches)
>
> ----------------------------------------------------------------
> qapi patches for 2018-03-01
>
> - Markus Armbruster: Modularize generated QAPI code
>
> ----------------------------------------------------------------
This version works -- applied, thanks.
-- PMM
prev parent reply other threads:[~2018-03-05 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:51 [Qemu-devel] [PULL v4 00/30] QAPI patches for 2018-03-01 Eric Blake
2018-03-02 19:51 ` [Qemu-devel] [PULL v4 23/30] qapi: Generate separate .h, .c for each module Eric Blake
2018-03-02 19:51 ` [Qemu-devel] [PULL v4 28/30] qapi: Move qapi-schema.json to qapi/, rename generated files Eric Blake
2018-03-05 12:15 ` Peter Maydell [this message]
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=CAFEAcA-WgS9nLC3iEQXi3p5Lhb1EDK-UEpty0ahgiG9ooPtLQQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eblake@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).