All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org,
	armbru@redhat.com, mreitz@redhat.com, stefanha@redhat.com,
	pbonzini@redhat.com, den@openvz.org, jsnow@redhat.com
Subject: Re: [Qemu-devel] [RFC v2] new, node-graph-based fleecing and backup
Date: Thu, 16 Aug 2018 12:58:25 -0500	[thread overview]
Message-ID: <515f3a0b-ff43-ca7d-155c-33ee329a74e3@redhat.com> (raw)
In-Reply-To: <b998a9a1-218a-77fa-a217-617213d99848@virtuozzo.com>

On 08/16/2018 12:28 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hmm, how should I properly set based-on, if there two series under this 
> one?
> 
> Based on:
>     [PATCH v3 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area
>     and
>     [PATCH 0/2] block: make .bdrv_close optional

patchew goes off mail ids, so I'll rewrite the above in a 
machine-readable format:

Based-on: <20180814121443.33114-1-vsementsov@virtuozzo.com>
Based-on: <20180814124320.39481-1-vsementsov@virtuozzo.com>


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-08-16 17:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 17:01 [Qemu-devel] [RFC v2] new, node-graph-based fleecing and backup Vladimir Sementsov-Ogievskiy
2018-08-16 15:05 ` no-reply
2018-08-16 17:28   ` Vladimir Sementsov-Ogievskiy
2018-08-16 17:58     ` Eric Blake [this message]
2018-08-16 15:09 ` no-reply
2018-08-17 18:21 ` Vladimir Sementsov-Ogievskiy
2018-08-17 20:56 ` no-reply
2018-08-17 21:01 ` no-reply
2018-08-17 21:50 ` Max Reitz
2018-08-20  9:42   ` Vladimir Sementsov-Ogievskiy
2018-08-20 13:32     ` Max Reitz
2018-08-20 14:49       ` Vladimir Sementsov-Ogievskiy
2018-08-20 17:25         ` Max Reitz
2018-08-20 18:30           ` Vladimir Sementsov-Ogievskiy
2018-08-21  9:29             ` Vladimir Sementsov-Ogievskiy

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=515f3a0b-ff43-ca7d-155c-33ee329a74e3@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@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.