From: Stefan Hajnoczi <stefanha@gmail.com>
To: Liu Yuan <namei.unix@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 RESENT 0/2] sheepdog: add user-defined redundancy option
Date: Thu, 21 Nov 2013 09:23:59 +0100 [thread overview]
Message-ID: <20131121082359.GA27039@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20131120172253.GB23252@ubuntu-precise>
On Thu, Nov 21, 2013 at 01:22:53AM +0800, Liu Yuan wrote:
> On Mon, Nov 18, 2013 at 01:58:50PM +0800, Liu Yuan wrote:
> > On Thu, Nov 07, 2013 at 10:56:36PM +0800, Liu Yuan wrote:
> > > v6:
> > > - update comment typo
> > > - remove is_number()
> >
> > Anyone pick this set up?
>
> Ping again. Without this two patches, qemu-img can't create|convert erasure coded
> images for sheepdog. I hope this two can go with release of v1.7 if possible.
QEMU entered "hard freeze" on 6th of November:
http://qemu-project.org/Planning/1.7
This means only bug fixes should be merged. Right now we're up to the
final -rc and the QEMU 1.7 release is scheduled for 22nd of November
(tomorrow).
The best I can do is review and apply it to the block-next branch for
qemu.git merge once QEMU 1.8 development begins next week.
Stefan
next prev parent reply other threads:[~2013-11-21 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 14:56 [Qemu-devel] [PATCH v6 RESENT 0/2] sheepdog: add user-defined redundancy option Liu Yuan
2013-11-07 14:56 ` [Qemu-devel] [PATCH v6 1/2] sheepdog: refactor do_sd_create() Liu Yuan
2013-11-07 14:56 ` [Qemu-devel] [PATCH v6 2/2] sheepdog: support user-defined redundancy option Liu Yuan
2013-11-18 5:58 ` [Qemu-devel] [PATCH v6 RESENT 0/2] sheepdog: add " Liu Yuan
2013-11-20 17:22 ` Liu Yuan
2013-11-21 8:23 ` Stefan Hajnoczi [this message]
2013-11-21 8:38 ` Liu Yuan
2013-11-21 8:28 ` Stefan Hajnoczi
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=20131121082359.GA27039@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--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).