From: Chris Mason <chris.mason@oracle.com>
To: "Ken D'Ambrosio" <ken@jots.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: CRFS?
Date: Wed, 16 Feb 2011 08:52:00 -0500 [thread overview]
Message-ID: <1297864176-sup-9579@think> (raw)
In-Reply-To: <c70f093c45470c7261e64b3570713d07.squirrel@webmail.jots.org>
Excerpts from Ken D'Ambrosio's message of 2011-02-15 12:35:47 -0500:
> Hey, all -- crfs (a network protocol that, I think, rides on top of btrfs)
> seemed like something kind of cool, but the Oracle page was last updated
> in '08. Is it truly dead, or just back-burnered?
Unfortunately it's heavily back-burnered. Zach Brown was leading crfs
and he got lured away by some evil startup (careful kids, those startup
people are tricky).
The best parts of crfs are the key range transfer stuff, and I hope to
use a mixture of the crfs code and ideas for the remote syncing tool.
-chris
prev parent reply other threads:[~2011-02-16 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 17:35 CRFS? Ken D'Ambrosio
2011-02-16 13:52 ` Chris Mason [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=1297864176-sup-9579@think \
--to=chris.mason@oracle.com \
--cc=ken@jots.org \
--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 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).