From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/6] Ocfs2-tools: Add a new tool 'o2info'.
Date: Mon, 25 Oct 2010 19:28:25 +0800 [thread overview]
Message-ID: <4CC569D9.2030401@oracle.com> (raw)
In-Reply-To: <1288004990-20076-1-git-send-email-tristan.ye@oracle.com>
Oops, sent the patches to a wrong mail list;-(
Resending them to 'ocfs2-tools-devel at oss.oracle.com' instead.
Sorry for the noise here.
Tristan.
Tristan Ye wrote:
> Now it's a good time to introduce the new tool 'o2info' since kernel
> part of OCFS2_IOC_INFO ioctl has been pulld upstream by linus.
>
> The following 6 patches have already got sunil's SOBs, and now they're
> trying to attract more reviewers before it goes to central repo with
> a modification of getting manual pages being introduced.
>
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
prev parent reply other threads:[~2010-10-25 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 11:09 [Ocfs2-devel] [PATCH 0/6] Ocfs2-tools: Add a new tool 'o2info' Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 1/6] O2info: Add all structures and commands OCFS2_IOC_INFO needed into ocfs2_ioctl.h Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 2/6] O2info: Build a main framework for o2info Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 3/6] O2info: Add '--cluster-coherent' option " Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 4/6] O2info: Add running codes for '--fs-features' Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 5/6] O2info: Add running codes for '--volinfo' Tristan Ye
2010-10-25 11:09 ` [Ocfs2-devel] [PATCH 6/6] O2info: Add --mkfs support for o2info Tristan Ye
2010-10-25 11:28 ` tristan [this message]
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=4CC569D9.2030401@oracle.com \
--to=tristan.ye@oracle.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.