qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: anthony@codemonkey.ws
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/6] QMP queue
Date: Wed, 18 Sep 2013 09:03:36 -0400	[thread overview]
Message-ID: <1379509422-29115-1-git-send-email-lcapitulino@redhat.com> (raw)

The following changes since commit 6c2679fc19560699679200fb42ab4659bcbe7f79:

  Merge remote-tracking branch 'kiszka/queues/slirp' into staging (2013-09-17 10:01:24 -0500)

are available in the git repository at:


  git://repo.or.cz/qemu/qmp-unstable.git queue/qmp

for you to fetch changes up to 7b5ce8db600a5d1842b9cb0cf8e8bb7af87fee10:

  QMP: qmp-events.txt: alphabetical order fix and other minor changes (2013-09-18 08:57:02 -0400)

----------------------------------------------------------------
Luiz Capitulino (6):
      QMP: add scripts/qmp
      QMP: fix qmp-commands.txt generation path
      QMP: QMP/ -> docs/qmp/
      QMP: Update README file
      QMP: Update qmp-spec.txt
      QMP: qmp-events.txt: alphabetical order fix and other minor changes

 Makefile                            |  6 +--
 QMP/README                          | 88 -------------------------------------
 docs/qmp/README                     | 87 ++++++++++++++++++++++++++++++++++++
 {QMP => docs/qmp}/qmp-events.txt    | 34 +++++++-------
 {QMP => docs/qmp}/qmp-spec.txt      | 65 ++++++++++++---------------
 {QMP => scripts/qmp}/qemu-ga-client |  0
 {QMP => scripts/qmp}/qmp            |  0
 {QMP => scripts/qmp}/qmp-shell      |  2 +-
 {QMP => scripts/qmp}/qmp.py         |  2 +-
 {QMP => scripts/qmp}/qom-fuse       |  0
 {QMP => scripts/qmp}/qom-get        |  0
 {QMP => scripts/qmp}/qom-list       |  0
 {QMP => scripts/qmp}/qom-set        |  0
 13 files changed, 137 insertions(+), 147 deletions(-)
 delete mode 100644 QMP/README
 create mode 100644 docs/qmp/README
 rename {QMP => docs/qmp}/qmp-events.txt (99%)
 rename {QMP => docs/qmp}/qmp-spec.txt (82%)
 rename {QMP => scripts/qmp}/qemu-ga-client (100%)
 rename {QMP => scripts/qmp}/qmp (100%)
 rename {QMP => scripts/qmp}/qmp-shell (99%)
 rename {QMP => scripts/qmp}/qmp.py (99%)
 rename {QMP => scripts/qmp}/qom-fuse (100%)
 rename {QMP => scripts/qmp}/qom-get (100%)
 rename {QMP => scripts/qmp}/qom-list (100%)
 rename {QMP => scripts/qmp}/qom-set (100%)

             reply	other threads:[~2013-09-18 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 13:03 Luiz Capitulino [this message]
2013-09-18 13:03 ` [Qemu-devel] [PULL 1/6] QMP: add scripts/qmp Luiz Capitulino
2013-09-18 13:03 ` [Qemu-devel] [PULL 2/6] QMP: fix qmp-commands.txt generation path Luiz Capitulino
2013-09-18 13:03 ` [Qemu-devel] [PULL 3/6] QMP: QMP/ -> docs/qmp/ Luiz Capitulino
2013-09-18 13:03 ` [Qemu-devel] [PULL 4/6] QMP: Update README file Luiz Capitulino
2013-09-18 13:03 ` [Qemu-devel] [PULL 5/6] QMP: Update qmp-spec.txt Luiz Capitulino
2013-09-18 13:03 ` [Qemu-devel] [PULL 6/6] QMP: qmp-events.txt: alphabetical order fix and other minor changes Luiz Capitulino
  -- strict thread matches above, loose matches on Subject: below --
2013-07-10 17:52 [Qemu-devel] [PULL 0/6] QMP queue Luiz Capitulino
2013-03-27 18:46 Luiz Capitulino

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=1379509422-29115-1-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).