From: Valdis.Kletnieks@vt.edu
To: Richard Weinberger <richard@nod.at>
Cc: mfasheh@suse.com, jlbec@evilplan.org, ocfs2-devel@oss.oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Sat, 15 Oct 2011 15:26:36 -0400 [thread overview]
Message-ID: <33629.1318706796@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 15 Oct 2011 19:49:43 +0200." <4E99C7B7.5060405@nod.at>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Sat, 15 Oct 2011 19:49:43 +0200, Richard Weinberger said:
> Am 15.10.2011 19:45, schrieb Valdis.Kletnieks@vt.edu:
> > On Sat, 15 Oct 2011 17:38:27 +0200, Richard Weinberger said:
> >> http://oss.oracle.com/projects/ocfs2/source.html states:
> >> "Active development on OCFS2 happens in the mainline kernel."
> > Put differently, why do you think 1.6.0 is available?
> OCFS2 1.6.3-1 and OCFS2 Tools 1.6.3-1 are the latest versions. The new
> features available in this release include Extended Attributes, POSIX
> ACLs, REFLINKs, Indexed Directories, Allocation Reservation, Metadata
> Checksums and User/Group Quotas."
Nice feature list, I can see why you want it. ;)
> Looks like it's only available for "Unbreakable Linux" subscribers.
> The development seems to be detached from mainline. :-(
Well, you have to admit it *is* an interesting business model - giving release
N to your customers and N-1 to the world. I just got totally mislead by the
quote from the Oracle site that said the development happens in mainline. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-15 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 15:38 Richard Weinberger
2011-10-15 17:45 ` Valdis.Kletnieks
2011-10-15 17:49 ` Richard Weinberger
2011-10-15 19:26 ` Valdis.Kletnieks [this message]
2011-10-15 21:03 ` Kyle Moffett
2011-10-15 21:12 ` Richard Weinberger
2011-10-15 21:25 ` Valdis.Kletnieks
2011-10-17 17:16 ` Mark Fasheh
2011-11-09 7:55 ` Joel Becker
2011-11-09 9:47 ` Richard Weinberger
2011-10-15 17:50 ` Randy Dunlap
2011-10-16 14:20 Xose Vazquez Perez
2011-10-16 14:55 Xose Vazquez Perez
2011-10-16 17:40 ` Sasha Levin
2011-10-16 22:07 ` Xose Vazquez Perez
2011-10-16 22:44 ` richard -rw- weinberger
2011-10-16 23:24 ` Sasha Levin
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=33629.1318706796@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®