From: Joel Becker <jlbec@evilplan.org>
To: Richard Weinberger <richard@nod.at>
Cc: Valdis.Kletnieks@vt.edu, mfasheh@suse.com,
ocfs2-devel@oss.oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Tue, 8 Nov 2011 23:55:10 -0800 [thread overview]
Message-ID: <20111109075508.GA331@noexit.corp.google.com> (raw)
In-Reply-To: <4E99C7B7.5060405@nod.at>
On Sat, Oct 15, 2011 at 07:49:43PM +0200, Richard Weinberger wrote:
> 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."
> >>
> >> But the mainline kernel seems to contain only version 1.5.0.
> >>
> >> Also the linux-next ocfs2 branch has only 1.5.0.
> >> git://oss.oracle.com/git/jlbec/linux-2.6.git linux-next
> >>
> >> Where can I get 1.6.0?
> >
> > Presumably, it's GPL, so you should be able to get a copy from the
> > person that told you that 1.6.0 exists. ;)
> >
> > Put differently, why do you think 1.6.0 is available?
>
> http://oss.oracle.com/projects/ocfs2/
>
> "OCFS2 1.6 RELEASE
>
> 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."
>
> Looks like it's only available for "Unbreakable Linux" subscribers.
> The development seems to be detached from mainline. :-(
Hello Folks,
Sorry I'm late to this game, but it's worth repeating.
Thankfully, you're just confused by shoddy version numbers. ALL
ocfs2 development happens in mainline. Any code that is in the 1.6.0
release, or any RPM release, started in mainline.
We don't really pay any attention to the version number reported
in the mainline code. It's said 1.5.0 for years now. Mainline is
versioned by the kernel release.
To repeat, ALL of the code in the 1.6.x RPM (or any RPM put out
by Oracle or SuSE) started in mainline, with the possible exception of
any trivial compatability fixes. If you have the latest Linus code, you
have the latest ocfs2 code.
Joel
--
"Same dancers in the same old shoes.
You get too careful with the steps you choose.
You don't care about winning but you don't want to lose
After the thrill is gone."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-11-09 8:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 15:38 OCFS2 1.6.0 for mainline? Richard Weinberger
2011-10-15 17:45 ` Valdis.Kletnieks
2011-10-15 17:49 ` Richard Weinberger
2011-10-15 19:26 ` Valdis.Kletnieks
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 [this message]
2011-11-09 9:47 ` Richard Weinberger
2011-10-15 17:50 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
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=20111109075508.GA331@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=Valdis.Kletnieks@vt.edu \
--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