From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Bryan Schumaker <bjschuma@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs-utils: add nfs.idmap
Date: Thu, 28 Oct 2010 11:45:33 -0400 [thread overview]
Message-ID: <4CC99A9D.10908@RedHat.com> (raw)
In-Reply-To: <1288280405.3194.44.camel@heimdal.trondhjem.org>
On 10/28/2010 11:40 AM, Trond Myklebust wrote:
> On Thu, 2010-10-28 at 11:27 -0400, Bryan Schumaker wrote:
>> On 10/28/2010 11:18 AM, Steve Dickson wrote:
>>> Hey Bryan,
>>>
>>> A couple nits.... which I will be more than willing to take of...
>>>
>>> 1) I would like to change the binary name from nfs.idmap to nfsidmap
>>> which is consistent with how the rest of the binaries are named.
>>> (i.e. binary names generally don't have any '.' or '-' in them)
>>>
>>> 2) Change the source directory from utils/nfs.idmap to
>>> utils/idmap which again makes it consistent with what
>>> is already there.
>>
>> These both sounds reasonable to me. I'll make a patch to modify the kernel documentation to reflect this.
>>>
>
> We just sent in one patch to change the name in the kernel docs, now the
> name is changing again?
I'll take the blame for that... I should have gotten into the
conversation earlier... sorry about that...
>
> Let's wait with this until an actual nfs-utils release is available, so
> we can also update the 'Documentation/Changes' file with the new minimal
> release version number.
Just to be clear... the kernel changes will be in the 2.6.37 kernel, correct?
steved.
next prev parent reply other threads:[~2010-10-28 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 12:48 [PATCH] nfs-utils: add nfs.idmap Bryan Schumaker
2010-10-26 17:17 ` Bryan Schumaker
2010-10-28 15:18 ` Steve Dickson
2010-10-28 15:27 ` Bryan Schumaker
2010-10-28 15:40 ` Trond Myklebust
2010-10-28 15:45 ` Steve Dickson [this message]
2010-10-28 15:51 ` Trond Myklebust
2010-10-28 16:04 ` Steve Dickson
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=4CC99A9D.10908@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@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 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.