From: Dmitri Nikulin <dnikulin@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs development plans
Date: Tue, 21 Apr 2009 18:56:36 +1000 [thread overview]
Message-ID: <3a7f57190904210156j519ffe7co40676783a6bde06d@mail.gmail.com> (raw)
In-Reply-To: <20090421094655.469cfb37.skraw@ithnet.com>
On Tue, Apr 21, 2009 at 5:46 PM, Stephan von Krawczynski
<skraw@ithnet.com> wrote:
> On Mon, 20 Apr 2009 12:38:57 -0400
> Chris Mason <chris.mason@oracle.com> wrote:
>
>> The short answer from my point of view is yes. =C2=A0This doesn't re=
ally
>> change the motivations for working on btrfs or the problems we're tr=
ying
>> to solve.
>
> ... which sounds logical to me. From looking at the project for a whi=
le one
> can see you are trying to solve problems that are not really linux' o=
nes...
Even so, I certainly hope that btrfs end up at least as reliable and
feature-complete as ZFS, if ZFS itself cannot be merged into Linux.
That's a big ask, but now that ZFS' IP has been imported into Oracle,
perhaps a lot of patent and copyright issues can be smoothed over,
giving btrfs a huge advantage relative to what it had before the
acquisition.
--=20
Dmitri Nikulin
Centre for Synchrotron Science
Monash University
Victoria 3800, Australia
--
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:[~2009-04-21 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 14:37 Btrfs development plans Chris Mason
2009-04-20 15:31 ` Tomasz Torcz
2009-04-20 16:10 ` Ahmed Kamal
2009-04-20 16:38 ` Chris Mason
2009-04-21 7:46 ` Stephan von Krawczynski
2009-04-21 8:56 ` Dmitri Nikulin [this message]
2009-04-21 15:05 ` ashford
2009-04-20 16:57 ` Andrey Kuzmin
2009-04-20 17:08 ` Gregory Maxwell
2009-04-20 17:18 ` Andrey Kuzmin
2009-04-20 17:20 ` Chris Mason
2009-04-20 17:39 ` Alex Elsayed
2009-04-21 2:27 ` Eric Anopolsky
2009-05-24 12:13 ` Chris Samuel
2009-04-20 18:42 ` Ric Wheeler
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=3a7f57190904210156j519ffe7co40676783a6bde06d@mail.gmail.com \
--to=dnikulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox