public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: mfasheh@suse.com, jlbec@evilplan.org
Cc: ocfs2-devel@oss.oracle.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: OCFS2 1.6.0 for mainline?
Date: Sat, 15 Oct 2011 17:38:27 +0200	[thread overview]
Message-ID: <4E99A8F3.50206@nod.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

Hi,

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?
When will it come to mainline?

*confused*,
//richard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-10-15 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15 15:38 Richard Weinberger [this message]
2011-10-15 17:45 ` OCFS2 1.6.0 for mainline? 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
  -- 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=4E99A8F3.50206@nod.at \
    --to=richard@nod.at \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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