From: Christoph Hellwig <hch@infradead.org>
To: Bruce Allan <bwa@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-nfs <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] add MODULE_DESCRIPTION to nfs module, update NFS references in MAINTAINERS
Date: Wed, 26 Jan 2005 08:05:47 +0000 [thread overview]
Message-ID: <20050126080547.GA6067@infradead.org> (raw)
In-Reply-To: <1106698790.4420.64.camel@w-bwa3.beaverton.ibm.com>
On Tue, Jan 25, 2005 at 04:19:50PM -0800, Bruce Allan wrote:
> Besides the NFS configuration comments in ./fs/Kconfig and the
> MAINTAINERS file (which might not be present on a system), can you
> suggest an alternative location to provide this pointer?
MAINTAINERS is exactly the right place.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-01-26 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 22:46 [PATCH] add MODULE_DESCRIPTION to nfs module, update NFS references in MAINTAINERS Bruce Allan
2005-01-25 23:08 ` Christoph Hellwig
2005-01-26 0:19 ` Bruce Allan
2005-01-26 8:05 ` Christoph Hellwig [this message]
2005-01-26 16:56 ` Bruce Allan
2005-01-26 19:44 ` Christoph Hellwig
2005-01-26 10:36 ` Neil Brown
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=20050126080547.GA6067@infradead.org \
--to=hch@infradead.org \
--cc=bwa@us.ibm.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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