From: Germano Percossi <germano.percossi@citrix.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-tools repository and documentation
Date: Tue, 9 Dec 2014 19:32:28 +0000 [thread overview]
Message-ID: <54874E4C.8040006@citrix.com> (raw)
Hi,
Sorry if this has been asked in the past but I did not
find anything in the archive.
It is not very clear to me where are the most up-to-date
ocfs-tools repository (both source code and
packages) and documentation.
For development I am looking at
https://oss.oracle.com/git/?p=ocfs2-tools.git;a=summary but the most
recent commit seems to be more than
1 year old.
I found an RPM (asking a colleague of mine to ask one of his contacts
in Oracle) here
http://public-yum.oracle.com/repo/OracleLinux/OL7/0/base/x86_64/getPackageSource/ocfs2-tools-1.8.0-16.el7.src.rpm.
When I inspected the content I found, comparing it to another package we
have, the following:
- a spec file (ok)
- some patches (ok)
- a tar.gz (ok but..)
The tar.gz is ocfs2-tools-1.8.0.tar.gz. The first strange thing is
that there are no versions tagged 1.8.0 in the git repo I am watching.
The other thing is, in our old RPM we have a tar.gz with the same name.
When I compared the content I found they differ just for the
vendor/rhel7 directory. Its content though is not in the git repository.
Is this repository the right one?
Similar doubts apply to documentation (referring to 1.6 version of the
tools and subversion as repository) and RPM repositories.
Would you please point me to the right development resources?
Thanks you,
Germano
next reply other threads:[~2014-12-09 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 19:32 Germano Percossi [this message]
2014-12-14 7:24 ` [Ocfs2-devel] ocfs2-tools repository and documentation Goldwyn Rodrigues
2014-12-15 18:47 ` Germano Percossi
2014-12-16 5:35 ` Srinivas Eeda
2014-12-16 17:43 ` Germano Percossi
2014-12-16 15:01 ` Goldwyn Rodrigues
2014-12-16 15:29 ` Goldwyn Rodrigues
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=54874E4C.8040006@citrix.com \
--to=germano.percossi@citrix.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 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.