From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main
Date: Wed, 28 Feb 2007 16:46:47 +0000 [thread overview]
Message-ID: <1172681207.11001.635.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <45E5ACB9.40200@redhat.com>
Hi,
Now in the git tree. Thanks,
Steve.
On Wed, 2007-02-28 at 11:24 -0500, Wendy Cheng wrote:
> ok, the following is the minimum changes to get NFSD going before we
> settle down this issue .. would appreciate this in the tree so other NFS
> related works can get done in parallel.
>
> -- Wendy
>
>
>
prev parent reply other threads:[~2007-02-28 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 4:51 [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main Wendy Cheng
2007-02-07 10:49 ` Steven Whitehouse
2007-02-07 22:35 ` Wendy Cheng
2007-02-07 23:37 ` Wendy Cheng
2007-02-08 9:42 ` Steven Whitehouse
2007-02-24 3:56 ` Wendy Cheng
2007-02-26 15:45 ` Steven Whitehouse
2007-02-26 16:11 ` Jonathan E Brassow
2007-02-26 17:16 ` Steven Whitehouse
2007-02-27 20:04 ` Wendy Cheng
2007-02-28 9:03 ` Steven Whitehouse
2007-02-28 16:24 ` Wendy Cheng
2007-02-28 16:26 ` Wendy Cheng
2007-02-28 16:46 ` Steven Whitehouse [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=1172681207.11001.635.camel@quoit.chygwyn.com \
--to=swhiteho@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).