From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs inode.c ops_file.c ...
Date: Sun, 02 Dec 2007 14:33:22 -0000 [thread overview]
Message-ID: <3F7A1ABB.9080700@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712020812560.24346@trider-g7>
Fabio M. Di Nitto wrote:
>
>> Yes .. but gfs(1)-kernel HEAD is currently broken ..
>
> I am adding Phillip in CC.
>
> So far he has been doing some work on gfs1 for Ubuntu, that includes a
> bunch of fixes. I was not able (mainly I did run out of time) to push
> them all.
>
> We have a git import based on a slightly old cvs head snapshot here:
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy-lum.git;a=summary
Glad to know people still working on this out-of-tree filesystem ...
Will look into this.
>
> There is a bit of merge that needs to be done between that tree and
> CVS, but there are some valuable fixes in there too that you want to
> take into account.
>
> Phillip knows more and better than me how those should be merged.
>
> Also.. do you know how is gfs1-kernel broken in HEAD?
Few things such as vector read/write .. but the most pressing issue is
that it won't compile due to newer kernel NFS changes.
>
>> Will review few proposed patches (including your NFS patches) and do
>> a clean-up first thing next week.
>
> That's probably not from me :) I never played around with NFS patches ;)
>
Well, maybe I remember it wrong ... Anyway, thanks for the info.
-- Wendy
next prev parent reply other threads:[~2007-12-02 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 21:48 [Cluster-devel] cluster/gfs-kernel/src/gfs inode.c ops_file.c wcheng
2007-12-01 4:08 ` Fabio Massimo Di Nitto
2007-12-02 2:51 ` Wendy Cheng
2007-12-02 7:18 ` Fabio M. Di Nitto
2007-12-02 14:33 ` Wendy Cheng [this message]
2007-12-03 13:54 ` Fabio M. Di Nitto
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=3F7A1ABB.9080700@redhat.com \
--to=wcheng@redhat.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.