From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OCFS2 1.6.0 for mainline?
Date: Mon, 17 Oct 2011 00:07:52 +0200 [thread overview]
Message-ID: <4E9B55B8.3090700@gmail.com> (raw)
In-Reply-To: <1318786832.31522.21.camel@lappy>
On 10/16/2011 07:40 PM, Sasha Levin wrote:
> On Sun, 2011-10-16 at 16:55 +0200, Xose Vazquez Perez wrote:
>> the latest is 1.8.0: http://public-yum.oracle.com/beta/repo/OracleLinux/OL6/uek2/x86_64/kernel-uek-2.6.39-100.0.12.el6uek.src.rpm
>>
>> No patch, just look at linux-2.6.39/fs/ocfs2/
>>
>> NO NO NO oracle!
> Oracle's git tree for OCFS2 is available at
> http://oss.oracle.com/git/?p=ocfs2-1.8.git;a=summary , and all the rest
> of their open source related trees are at http://oss.oracle.com/git/ .
last change in git was *ONE year* ago: 12 Oct 2010
kernel-uek-2.6.39-100.0.12.el6uek.src.rpm is two weeks old.
Are you sure is the same code in git and src.rpm ?
Are going oracle to play also this way with btrfs ?
next prev parent reply other threads:[~2011-10-16 22:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 14:55 OCFS2 1.6.0 for mainline? Xose Vazquez Perez
2011-10-16 17:40 ` Sasha Levin
2011-10-16 22:07 ` Xose Vazquez Perez [this message]
2011-10-16 22:44 ` richard -rw- weinberger
2011-10-16 23:24 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2011-10-16 14:20 Xose Vazquez Perez
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
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
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=4E9B55B8.3090700@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.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.