From: Valdis.Kletnieks@vt.edu
To: Sage Weil <sage@newdream.net>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph distributed file system client for 2.6.33
Date: Sat, 19 Dec 2009 00:33:17 -0500 [thread overview]
Message-ID: <14397.1261200797@localhost> (raw)
In-Reply-To: Your message of "Fri, 18 Dec 2009 12:54:02 PST." <Pine.LNX.4.64.0912181140370.26094@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Fri, 18 Dec 2009 12:54:02 PST, Sage Weil said:
> I would still like to see ceph merged for 2.6.33. It's certainly not
> production ready, but it would be greatly beneficial to be in mainline for
> the same reasons other file systems like btrfs and exofs were merged
> early.
Is the on-the-wire protocol believed to be correct, complete, and stable? How
about any userspace APIs and on-disk formats? In other words..
> > The git tree includes the full patchset posted in October and incremental
> > changes since then. I've tried to cram in all the anticipated protocol
> > changes, but the file system is still strictly EXPERIMENTAL and is marked
Anything left dangling on the changes?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-12-19 5:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 23:25 [GIT PULL] Ceph distributed file system client for 2.6.33 Sage Weil
2009-12-18 20:54 ` Sage Weil
2009-12-18 21:38 ` Linus Torvalds
2009-12-18 23:15 ` Jim Garlick
2009-12-19 11:01 ` Andi Kleen
2009-12-21 16:42 ` Sage Weil
2009-12-21 17:06 ` ceph in v2.6.33? Sage Weil
2009-12-21 18:20 ` Rocky Shek
2009-12-28 7:05 ` Anton
2009-12-28 17:42 ` Sage Weil
2010-01-05 9:30 ` Jerker Nyberg
2010-01-01 21:41 ` Roland Rabben
2010-01-03 17:41 ` Rocky Shek
2010-02-09 20:43 ` [GIT PULL] Ceph distributed file system client for 2.6.33 Josef Bacik
2009-12-19 5:33 ` Valdis.Kletnieks [this message]
2009-12-21 16:42 ` Sage Weil
2009-12-21 18:04 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2009-12-28 0:17 Craig Dunwoody
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=14397.1261200797@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
--cc=torvalds@linux-foundation.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.