From: Mark Fasheh <mfasheh@suse.de>
To: Richard Weinberger <richard@nod.at>
Cc: Kyle Moffett <kyle@moffetthome.net>,
Valdis.Kletnieks@vt.edu, jlbec@evilplan.org,
ocfs2-devel@oss.oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
license-violation@gpl-violations.org
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Mon, 17 Oct 2011 10:16:09 -0700 [thread overview]
Message-ID: <20111017171609.GD23779@wotan.suse.de> (raw)
In-Reply-To: <4E99F74C.80900@nod.at>
On Sat, Oct 15, 2011 at 11:12:44PM +0200, Richard Weinberger wrote:
> >> 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. ;)
> >
> > If someone who has a copy of Oracle's "Unbreakable Linux" can get
> > ahold of the sources, please put them in GIT somewhere for the rest of
> > us to access; it *is* GPLed software after all. Otherwise, please
> > distribute the binaries to the rest of us and we will obtain the
> > sources on our own. I can't find any published information on their
> > website about how to obtain the sources, so someone will have to
> > contact them directly.
>
> I found this src.rpm:
> http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/x86_64/kernel-uek-2.6.32-100.34.1.el6uek.src.rpm
>
> linux-2.6.32/fs/ocfs2 contains OCFS2 1.6.3.
>
> Mark, Joel, can you please port this "release" to mainline?
>
> Thanks,
> //richard
There's no point, everything in mainline is in that release (1.6.3). If
there's anything not in mainline that's there it should only be because of
the following reasons:
- It is not suitable for mainline (the datavolume hack is one example)
- It just hasn't been pushed yet but is in Joel's tree or is on the
list waiting review.
If you see otherwise of course, please let us all know - including the
Oracle folks they really are keeping this upstream.
I think you all are being confused by two things:
- meaningless version numbers - we don't care too much about version
numbers in the upstream code since we can go about that by looking at
kernel version. Oracle (and SUSE) on the other hand like to increase
numbers for obvious customer reasons. Hence the upstream version just
looks 'old'.
- The confusing way in which Ocfs2 is presented on the oss.oracle.com site.
There can be improvements in how things are worded and presented but that's
really out of my control.
Again, let us know if you find anything that contradicts what I just wrote.
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2011-10-17 17:16 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 [this message]
2011-11-09 7:55 ` Joel Becker
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=20111017171609.GD23779@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jlbec@evilplan.org \
--cc=kyle@moffetthome.net \
--cc=license-violation@gpl-violations.org \
--cc=linux-kernel@vger.kernel.org \
--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