From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com, stefanha@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] backup improvements part 1
Date: Wed, 29 Nov 2017 09:27:52 +0800 [thread overview]
Message-ID: <20171129012752.GC8889@lemon> (raw)
In-Reply-To: <20171128194413.GJ25110@localhost.localdomain>
On Tue, 11/28 14:44, Jeff Cody wrote:
> > Yes, I can bring in through my tree, unless Fam prefers to have it - I'll
> > pull it in via my block-next branch.
> >
>
> Rather than keep this on my email queue:
>
> Applied to my block-next branch:
>
> git://github.com/codyprime/qemu-kvm-jtc block-next
Yes, thanks, sorry for not noticing you're pending on my response.
Fam
next prev parent reply other threads:[~2017-11-29 1:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 13:53 [Qemu-devel] [PATCH v2 0/5] backup improvements part 1 Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 1/5] hbitmap: add next_zero function Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 2/5] backup: move from done_bitmap to copy_bitmap Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 3/5] backup: init copy_bitmap from sync_bitmap for incremental Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 4/5] backup: simplify non-dirty bits progress processing Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 5/5] backup: use copy_bitmap in incremental backup Vladimir Sementsov-Ogievskiy
2017-10-12 14:31 ` [Qemu-devel] [PATCH v2 0/5] backup improvements part 1 no-reply
2017-10-13 7:37 ` Vladimir Sementsov-Ogievskiy
2017-10-13 13:15 ` [Qemu-devel] iotest 77 failure [was: [PATCH v2 0/5] backup improvements part 1] Eric Blake
2017-10-31 10:26 ` [Qemu-devel] ping Re: [PATCH v2 0/5] backup improvements part 1 Vladimir Sementsov-Ogievskiy
2017-11-02 20:52 ` John Snow
2017-11-03 5:37 ` Vladimir Sementsov-Ogievskiy
2017-11-07 0:26 ` [Qemu-devel] " John Snow
2017-11-13 22:41 ` John Snow
2017-11-14 5:00 ` Jeff Cody
2017-11-28 19:44 ` Jeff Cody
2017-11-29 1:27 ` Fam Zheng [this message]
2017-11-29 1:26 ` Fam Zheng
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=20171129012752.GC8889@lemon \
--to=famz@redhat.com \
--cc=den@openvz.org \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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.