Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH RFC 0/5] Possible changes to nfs-utils junction support
Date: Thu, 7 Dec 2023 14:36:33 -0500	[thread overview]
Message-ID: <3dac71e2-e8a2-4c40-9d05-9369253914f3@redhat.com> (raw)
In-Reply-To: <170050610386.123525.8429348635736141592.stgit@manet.1015granger.net>



On 11/20/23 1:53 PM, Chuck Lever wrote:
> Bruce suggested, years ago, that the nfsref command should become
> the premier administrative interface for managing NFSD's referral
> behavior.
> 
> Towards that end, some clean-up is needed for the nfsref command in
> nfs-utils, which is presented for review here.
> 
> I'm hesitant to introduce more documentation at this time for the
> refer= and replica= export options if we plan to remove them in the
> medium term.
> 
> ---
> 
> Chuck Lever (5):
>        junction: Replace xmlParseMemory
>        junction: Remove xmlIndentTreeOutput
>        nfsref: Remove unneeded #include in utils/nfsref/nfsref.c
>        nfsref: Improve nfsref(5)
>        configure: Make --enable-junction=yes the default
> 
> 
>   configure.ac            |  6 ++---
>   support/junction/xml.c  |  3 +--
>   utils/nfsref/nfsref.c   |  2 --
>   utils/nfsref/nfsref.man | 60 +++++++++++++++++++++--------------------
>   4 files changed, 35 insertions(+), 36 deletions(-)
> 
> --
> Chuck Lever
> 
Committed... (tag: nfs-utils-2-7-1-rc2)

steved.


      parent reply	other threads:[~2023-12-07 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 18:53 [PATCH RFC 0/5] Possible changes to nfs-utils junction support Chuck Lever
2023-11-20 18:53 ` [PATCH RFC 1/5] junction: Replace xmlParseMemory Chuck Lever
2023-11-20 18:53 ` [PATCH RFC 2/5] junction: Remove xmlIndentTreeOutput Chuck Lever
2023-11-20 18:53 ` [PATCH RFC 3/5] nfsref: Remove unneeded #include in utils/nfsref/nfsref.c Chuck Lever
2023-11-20 18:53 ` [PATCH RFC 4/5] nfsref: Improve nfsref(5) Chuck Lever
     [not found]   ` <20250125200217.7A01.409509F4@e16-tech.com>
2025-01-25 16:09     ` Chuck Lever
2023-11-20 18:54 ` [PATCH RFC 5/5] configure: Make --enable-junction=yes the default Chuck Lever
2023-11-20 18:58 ` [PATCH RFC 0/5] Possible changes to nfs-utils junction support Chuck Lever III
2023-11-21 15:48   ` Chuck Lever III
2023-12-07 19:36 ` 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=3dac71e2-e8a2-4c40-9d05-9369253914f3@redhat.com \
    --to=steved@redhat.com \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.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