qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 0/3] qga: support fsfreeze'ing specific mounts


From: Michael Roth
Subject: Re: [Qemu-devel] [PULL 0/3] qga: support fsfreeze'ing specific mounts
Date: Fri, 08 Aug 2014 07:59:25 -0500
User-agent: alot/0.3.4

Quoting Peter Maydell (2014-08-08 06:12:34)
> On 7 August 2014 23:18, Eric Blake <address@hidden> 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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]