From: Zdenek Kabelac <zkabelac@redhat.com>
To: Gionatan Danti <g.danti@assyoma.it>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM send/receive support?
Date: Mon, 5 Jun 2017 11:11:59 +0200 [thread overview]
Message-ID: <03054980-651b-577e-e7eb-cba39d152da9@redhat.com> (raw)
In-Reply-To: <4495a5e6-6c92-97c0-c4ba-11d8a78893da@assyoma.it>
Dne 5.6.2017 v 10:48 Gionatan Danti napsal(a):
> Hi Zdenek,
> thanks for pointing me to thin_delta - very useful utility. Maybe I can code
> around it...
>
> As an additional question, is direct lvm2 support for send/receive planned, or
> not?
Hi
It will certainly happen - just not sure in which year...
ATM higher prio tasks are on the table.
Regards
Zdenek
prev parent reply other threads:[~2017-06-05 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 8:11 [linux-lvm] LVM send/receive support? Gionatan Danti
2017-06-05 8:44 ` Zdenek Kabelac
2017-06-05 8:48 ` Gionatan Danti
2017-06-05 9:11 ` Zdenek Kabelac [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=03054980-651b-577e-e7eb-cba39d152da9@redhat.com \
--to=zkabelac@redhat.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@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).