From: Steve Dickson <SteveD@RedHat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: ANNOUNCE: nfs-utils-2.3.2 released.
Date: Thu, 24 May 2018 13:30:32 -0400 [thread overview]
Message-ID: <ae4d2ce7-ca45-9f65-54a2-bbb44ca4c34d@RedHat.com> (raw)
Hello,
nfs-utils-2.3.2 has just been released.
Along with the usual bug fixes:
* libjunction support was added.
* The nfsref command was added that administers junctions
* Most compile warnings are now fatal errors.
* The nfsconf command was added that dump, gets and
test setting in /etc/nfs.conf
The tarballs can be found in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.3.2/
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.3.2
The change log is in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.3.2/2.3.2-Changelog
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.3.2/
The git tree is at:
git://linux-nfs.org/~steved/nfs-utils
Please send comments/bugs to linux-nfs@vger.kernel.org
steved.
reply other threads:[~2018-05-24 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ae4d2ce7-ca45-9f65-54a2-bbb44ca4c34d@RedHat.com \
--to=steved@redhat.com \
--cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).