From: Stephan von Krawczynski <skraw@ithnet.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Ahmed Kamal <email.ahmedkamal@googlemail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs development plans
Date: Tue, 21 Apr 2009 09:46:55 +0200 [thread overview]
Message-ID: <20090421094655.469cfb37.skraw@ithnet.com> (raw)
In-Reply-To: <1240245537.16213.59.camel@think.oraclecorp.com>
On Mon, 20 Apr 2009 12:38:57 -0400
Chris Mason <chris.mason@oracle.com> wrote:
> On Mon, 2009-04-20 at 18:10 +0200, Ahmed Kamal wrote:
> > > But now Oracle can re-license Solaris and merge ZFS with btrfs.
> > > Just kidding, I don't think it would be technically feasible.
> > >
> >
> > May I suggest the name "ZbtrFS" :)
> > Sorry couldn't resist. On a more serious note though, is there any
> > technical benefits that justify continuing to push money in btrfs
>
> The short answer from my point of view is yes. This doesn't really
> change the motivations for working on btrfs or the problems we're trying
> to solve.
... which sounds logical to me. From looking at the project for a while one
can see you are trying to solve problems that are not really linux' ones...
--
Regards,
Stephan
next prev parent reply other threads:[~2009-04-21 7:46 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 [this message]
2009-04-21 8:56 ` Dmitri Nikulin
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=20090421094655.469cfb37.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=chris.mason@oracle.com \
--cc=email.ahmedkamal@googlemail.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