From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>, Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Tomoki Sekiyama <tomoki.sekiyama@hds.com>
Subject: Re: [Qemu-devel] [PULL 0/3] qga: support fsfreeze'ing specific mounts
Date: Fri, 08 Aug 2014 07:59:25 -0500 [thread overview]
Message-ID: <20140808125925.24488.9080@loki> (raw)
In-Reply-To: <CAFEAcA83Y3L0-gmk4B0oYeJSz93h2D+871kmh3f_3cBdydd6Eg@mail.gmail.com>
Quoting Peter Maydell (2014-08-08 06:12:34)
> On 7 August 2014 23:18, Eric Blake <eblake@redhat.com> wrote:
> > On 08/07/2014 04:10 PM, Michael Roth wrote:
> >> Please pull the following changes, which add a new guest-fsfreeze-freeze-list
> >> command to qemu-ga that supports specifying specific mounts to freeze, and
> >> improves the introspection information from guest-info by explicitly
> >> blacklisting/reporting commands that aren't supported on a particular guest.
> >>
> >> The following changes since commit 2ee55b8351910e5dd898f52415064a4c5479baba:
> >>
> >> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2014-08-07 14:54:47 +0100)
> >>
> >> are available in the git repository at:
> >>
> >>
> >> git://github.com/mdroth/qemu.git qga-pull-2014-08-07
> >>
> >> for you to fetch changes up to 30043300803c1a16e3acedf973fc20a849e3be6e:
> >>
> >> qga: Disable unsupported commands by default (2014-08-07 16:59:41 -0500)
> >>
> >> ----------------------------------------------------------------
> >> Tomoki Sekiyama (3):
> >> qga: Add guest-fsfreeze-freeze-list command
> >> qga: Add guest-get-fsinfo command
> >> qga: Disable unsupported commands by default
> >
> > This series includes .json patches that call out 2.1 even though it is
> > 2.2 material; I'm okay with deferring the fix to a followup patch if it
> > is easier to not have to bother with a v2 pull request.
>
> Michael, did you update the branch with the 2.1 to 2.2 changes?
> It looks like the json says 2.2 now, but I don't see a new pull
> request email...
I tried to do a ninja edit a few minutes after sending but I think Eric
caught it just before I pushed :) Will send a v2 with a new pull branch
to be clear.
>
> thanks
> -- PMM
prev parent reply other threads:[~2014-08-08 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 22:10 [Qemu-devel] [PULL 0/3] qga: support fsfreeze'ing specific mounts Michael Roth
2014-08-07 22:10 ` [Qemu-devel] [PATCH 1/3] qga: Add guest-fsfreeze-freeze-list command Michael Roth
2014-08-07 22:10 ` [Qemu-devel] [PATCH 2/3] qga: Add guest-get-fsinfo command Michael Roth
2014-08-07 22:10 ` [Qemu-devel] [PATCH 3/3] qga: Disable unsupported commands by default Michael Roth
2014-08-07 22:18 ` [Qemu-devel] [PULL 0/3] qga: support fsfreeze'ing specific mounts Eric Blake
2014-08-08 11:12 ` Peter Maydell
2014-08-08 12:59 ` Michael Roth [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=20140808125925.24488.9080@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tomoki.sekiyama@hds.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.