From: Steve Dickson <SteveD@redhat.com>
To: Michael Weiser <M.Weiser@science-computing.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 post-1.2.2 nfs-utils client fails to mount from pre-1.2.3 nfs-utils server
Date: Thu, 12 Apr 2012 10:43:20 -0400 [thread overview]
Message-ID: <4F86EA08.5000308@RedHat.com> (raw)
In-Reply-To: <20120329140226.GB1362@science-computing.de>
On 03/29/2012 10:02 AM, Michael Weiser wrote:
> Hi Steve,
>
> On Tue, Mar 20, 2012 at 06:44:18PM +0100, Michael Weiser wrote:
>
>>>> If nobody objects, I'd resubmit my patch to gssd with some cleanup and
>>>> documentation.\
>>> No, Please do...
>> Here's the patch. Is there any special procedure to follow to get it
>> committed?
>
> How do I go about getting this committed?
My bad... I'm looking into this now....
>
>> I just noticed that while the code bits are optional based on
>> HAVE_SET_ALLOWABLE_ENCTYPES, the man page part isn't. I've got no idea,
>> how to go about that.
I'm think we should remove all those defines and have the code enabled
by default. The main reason is defines like that just clutter up the
code, plus there would be a needed for another configuration flag
which I think is a bit over kill...
steved.
next prev parent reply other threads:[~2012-04-12 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 20:02 NFSv4 post-1.2.2 nfs-utils client fails to mount from pre-1.2.3 nfs-utils server Michael Weiser
2012-03-12 20:24 ` Jim Rees
2012-03-12 21:10 ` Kevin Coffman
2012-03-12 21:57 ` Michael Weiser
2012-03-13 13:51 ` Kevin Coffman
2012-03-13 14:42 ` Michael Weiser
2012-03-13 18:53 ` Kevin Coffman
2012-03-14 13:48 ` Michael Weiser
2012-03-19 13:00 ` Michael Weiser
2012-03-20 11:27 ` Steve Dickson
2012-03-20 17:44 ` Michael Weiser
2012-03-29 14:02 ` Michael Weiser
2012-04-12 14:43 ` Steve Dickson [this message]
2012-04-12 15:49 ` Michael Weiser
2012-04-12 16:02 ` Steve Dickson
2012-04-13 12:34 ` Michael Weiser
2012-04-16 10:51 ` 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=4F86EA08.5000308@RedHat.com \
--to=steved@redhat.com \
--cc=M.Weiser@science-computing.de \
--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).