From: Arne Jansen <sensille@gmx.net>
To: Gabriel <g2p.code@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: find-new possibility of showing modified and deleted files/directories
Date: Thu, 01 Nov 2012 12:29:36 +0100 [thread overview]
Message-ID: <50925D20.7040603@gmx.net> (raw)
In-Reply-To: <k6tkp5$oa5$1@ger.gmane.org>
On 01.11.2012 12:00, Gabriel wrote:
> On Thu, 01 Nov 2012 06:06:57 +0100, Arne Jansen wrote:
>> On 11/01/2012 02:28 AM, Shane Spencer wrote:
>>> That's Plan B. I'll be making a btrfs stream decoder and doing in
>>> place edits. I need to move stuff around to other filesystem types
>>> otherwise I'd just store the stream or apply the stream to a remote
>>> snapshot.
>
>> That's the whole point of the btrfs-send design: It's very easy to
>> receive on different filesystems. A generic receiver is in preparation.
>> And to make it even more generic: A sender using the same stream format
>> is also in preparation for zfs.
>
> Consider the rsync bundle format as well.
> That should provide interoperability with any filesystem.
Rsync is an interactive protocol. The idea with send/receive is that
the stream can be generated without any interactions with receiver.
You can store the stream somewhere, or replay it to many destinations.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-01 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 23:25 find-new possibility of showing modified and deleted files/directories Shane Spencer
[not found] ` <CAE5mzvi0jLAm_pp0YzD=o2W86jrPSnNw3Z+3UFq9ZY1joynCew@mail.gmail.com>
2012-11-01 1:28 ` Shane Spencer
2012-11-01 5:06 ` Arne Jansen
2012-11-01 11:00 ` Gabriel
2012-11-01 11:29 ` Arne Jansen [this message]
2012-11-01 15:06 ` Gabriel
2012-11-01 16:27 ` Shane Spencer
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=50925D20.7040603@gmx.net \
--to=sensille@gmx.net \
--cc=g2p.code@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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.