From: Kevin Wolf <kwolf@redhat.com>
To: Liu Yuan <namei.unix@gmail.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [PATCH v4 0/2] fix 'qemu-img snapshot -a' operation for sheepdog
Date: Mon, 10 Jun 2013 10:58:14 +0200 [thread overview]
Message-ID: <20130610085813.GA3636@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1370627666-6689-1-git-send-email-namei.unix@gmail.com>
Am 07.06.2013 um 19:54 hat Liu Yuan geschrieben:
> v4:
> - fix savevm, pass current vdi_id instead of parent_vdi_id
>
> v3:
> - fix sheepdog's loadvm handling, don't rely on the write to create branch
>
> v2:
> - add the comment to make things more clear
> - call sd_create_branch() after s->is_snapshot = true because after calling
> sd_create_branch, it is not snapshot anymore.
>
> Nothing big, just two simple patches to enable this commind for sheepdog.
>
> Cc: qemu-devel@nongnu.org
> Cc: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
>
> Liu Yuan (2):
> sheepdog: fix snapshot tag initialization
> sheepdog: support 'qemu-img snapshot -a'
>
> block/sheepdog.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2013-06-10 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:54 [Qemu-devel] [PATCH v4 0/2] fix 'qemu-img snapshot -a' operation for sheepdog Liu Yuan
2013-06-07 17:54 ` [Qemu-devel] [PATCH 1/2] sheepdog: fix snapshot tag initialization Liu Yuan
2013-06-07 17:54 ` [Qemu-devel] [PATCH v4 2/2] sheepdog: support 'qemu-img snapshot -a' Liu Yuan
2013-06-10 8:58 ` Kevin Wolf [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=20130610085813.GA3636@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@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 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).