From: Christoph Hellwig <hch@infradead.org>
To: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: NFS and NFSv4 lists?
Date: Thu, 13 Aug 2009 13:49:24 -0400 [thread overview]
Message-ID: <20090813174923.GA15213@infradead.org> (raw)
Is there really a reason to keep a separate NFSv4 mailing list? v4
support is part of the same nfs/nfsd modules and quite deeply
interwinded with the v2/v3 code. It seems most posts to the NFSv4 list
get cross-posted to the regular nfs list anyway.
next reply other threads:[~2009-08-13 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 17:49 Christoph Hellwig [this message]
2009-08-13 18:07 ` NFS and NFSv4 lists? Trond Myklebust
2009-08-13 18:14 ` Christoph Hellwig
2009-08-13 18:32 ` J. Bruce Fields
2009-08-13 18:45 ` 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=20090813174923.GA15213@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox