From: Steve Dickson <steved@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] autoconf: don't build nfsdcltrack by default
Date: Sat, 23 Nov 2024 14:52:56 -0500 [thread overview]
Message-ID: <603c6c03-1e98-48e2-b149-73720661f11d@redhat.com> (raw)
In-Reply-To: <20231127-master-v1-1-5786ec1c6d38@kernel.org>
On 11/27/23 10:18 AM, Jeff Layton wrote:
> Now that we've started the process to remove legacy v4 client tracking
> methods, let's stop building nfsdcltrack by default.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> configure.ac | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Committed... (tag: nfs-utils-2-8-2-rc3)
steved.
>
> diff --git a/configure.ac b/configure.ac
> index 93a1202807ea..62c833cc2409 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -248,9 +248,9 @@ AC_ARG_ENABLE(nfsrahead,
> fi
>
> AC_ARG_ENABLE(nfsdcltrack,
> - [AS_HELP_STRING([--disable-nfsdcltrack],[disable NFSv4 clientid tracking programs @<:@default=no@:>@])],
> + [AS_HELP_STRING([--enable-nfsdcltrack],[enable NFSv4 clientid tracking programs @<:@default=no@:>@])],
> enable_nfsdcltrack=$enableval,
> - enable_nfsdcltrack="yes")
> + enable_nfsdcltrack="no")
>
> AC_ARG_ENABLE(nfsv4server,
> [AS_HELP_STRING([--enable-nfsv4server],[enable support for NFSv4 only server @<:@default=no@:>@])],
>
> ---
> base-commit: cc5cccbb9f24a2324f50a5cb4c29d83fdf6b1f90
> change-id: 20231127-master-5ef1c15da9c4
>
> Best regards,
prev parent reply other threads:[~2024-11-23 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:18 [PATCH] autoconf: don't build nfsdcltrack by default Jeff Layton
2023-12-07 19:42 ` Steve Dickson
2023-12-07 20:14 ` Jeff Layton
2023-12-08 10:53 ` Steve Dickson
2024-11-23 19:52 ` Steve Dickson [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=603c6c03-1e98-48e2-b149-73720661f11d@redhat.com \
--to=steved@redhat.com \
--cc=jlayton@kernel.org \
--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