Re: OCFS2 1.6.0 for mainline?

Richard Weinberger
2011-11-09T09:47:38Z

On Tue, 8 Nov 2011 23:55:10 -0800, Joel Becker <jlbec@evilplan.org>
wrote:
> 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.
>

Thanks for the clarification!

//richard