From: Christoph Hellwig <hch@infradead.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: "NFS: v4 server 127.0.0.1 does not accept raw uid/gids. Reenabling the idmapper."
Date: Mon, 11 Nov 2013 13:01:15 -0800 [thread overview]
Message-ID: <20131111210115.GA13942@infradead.org> (raw)
In-Reply-To: <C75D4AA2-1EC2-4623-B19A-7F7C7F19C24D@netapp.com>
On Mon, Nov 11, 2013 at 07:11:34PM +0000, Myklebust, Trond wrote:
> The above message should be harmless.
Any reason to keep it around then?
prev parent reply other threads:[~2013-11-11 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 18:40 "NFS: v4 server 127.0.0.1 does not accept raw uid/gids. Reenabling the idmapper." Christoph Hellwig
2013-11-11 19:11 ` Myklebust, Trond
2013-11-11 21:01 ` Christoph Hellwig [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=20131111210115.GA13942@infradead.org \
--to=hch@infradead.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@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 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).