From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Shantanu Goel" <Shantanu.Goel@lehman.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename]
Date: 28 Nov 2003 11:45:01 -0500 [thread overview]
Message-ID: <shsu14oh27m.fsf@charged.uio.no> (raw)
In-Reply-To: <3FC763A5.6030404@lehman.com>
>>>>> " " == Shantanu Goel <Shantanu.Goel@lehman.com> writes:
> I initially mailed this to the NFS mailing list on
> sourceforge.net but it doesn't seem to have made it through.
It's not a critical bugfix. It will make it in, but not while the
current code-freeze is in place.
Cheers,
Trond
next prev parent reply other threads:[~2003-11-28 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 15:03 [Fwd: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename] Shantanu Goel
2003-11-28 16:45 ` Trond Myklebust [this message]
2003-11-28 16:50 ` Shantanu Goel
2003-11-28 17:05 ` Trond Myklebust
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=shsu14oh27m.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Shantanu.Goel@lehman.com \
--cc=linux-kernel@vger.kernel.org \
/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.