From: Mark Fasheh <mfasheh@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 00/00] Implement quotas for OCFS2 (version 2)
Date: Wed, 29 Oct 2008 15:58:32 -0700 [thread overview]
Message-ID: <20081029225832.GH15154@wotan.suse.de> (raw)
In-Reply-To: <12248859043309-git-send-email-jack@suse.cz>
On Sat, Oct 25, 2008 at 12:05:04AM +0200, Jan Kara wrote:
> Hello,
>
> the following patch series implements quotas for OCFS2. The patch
> series is based on:
> git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git linux-next
Great, thanks for posting these again.
> I've adressed Joel's comments, also node recovery is now fully working
> and I've fixed a few issues I found during my testing. So I'm currently
> not aware of any bugs. Please review, test, comment. Thanks.
How are we going to handle the vfs patches? I think realistically, they
should just all go into the merge_window branch of ocfs2.git along with the
Ocfs2 patches to add quoata support (and make use of the VFS features you
added). The VFS patches at least though, should probably get posted to
linux-fsdevel before I pick them up.
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2008-10-29 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 22:05 [Ocfs2-devel] [PATCH 00/00] Implement quotas for OCFS2 (version 2) Jan Kara
2008-10-27 7:22 ` tristan.ye
2008-10-27 9:08 ` tristan.ye
2008-10-27 11:23 ` Jan Kara
2008-10-27 11:23 ` Jan Kara
[not found] ` <1225159789.6555.24.camel@tristan-laptop.cn.oracle.com>
2008-10-28 11:23 ` tristan.ye
2008-10-29 1:57 ` Jan Kara
2008-10-29 2:32 ` tristan.ye
2008-10-29 22:58 ` Mark Fasheh [this message]
2008-10-30 5:02 ` Jan Kara
2008-10-30 23:32 ` Mark Fasheh
2008-11-06 1:09 ` Mark Fasheh
2008-11-20 19:33 ` Jan Kara
2008-11-24 20:50 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2008-10-24 22:07 Jan Kara
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=20081029225832.GH15154@wotan.suse.de \
--to=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 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.