From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 version issue
Date: Tue, 1 Sep 2015 05:32:16 -0500 [thread overview]
Message-ID: <55E57EB0.8060207@suse.de> (raw)
In-Reply-To: <55E50BF8.50004@oracle.com>
Hi Junxiao,
On 08/31/2015 09:22 PM, Junxiao Bi wrote:
> Hi Goldwyn,
>
> Ocfs2 kernel version is removed from commit
> ff8fb335221e2c446b0d4cbea26be371fd2feb64 ("ocfs2: remove versioning
> information"), but Oracle CRS depends on this version, and this made
> Oracle CRS can't be installed. So i think we should revert this commit
> and sync this version with ocfs2-tools. Do you have any other concern
> about this?
We removed the version because it did not make sense. Even if we put in
the version back we will have to maintain it and will have a similar
case where the version number in the kernel is way behind the tools
versions because of lack of updating. Add to it the confusion of users
who would not know which version to quote.
I suggest the Oracle CRS should be modified to use the kernel version as
opposed to the ocfs2 kernel module specific versions.
--
Goldwyn
next prev parent reply other threads:[~2015-09-01 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 2:22 [Ocfs2-devel] ocfs2 version issue Junxiao Bi
2015-09-01 10:32 ` Goldwyn Rodrigues [this message]
2015-09-02 0:08 ` Srinivas Eeda
2015-09-02 12:34 ` Goldwyn Rodrigues
2015-09-02 17:20 ` Darrick J. Wong
2015-09-02 1:15 ` Junxiao Bi
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=55E57EB0.8060207@suse.de \
--to=rgoldwyn@suse.de \
--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 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.