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.4.1 released.
Date: Mon, 10 Jun 2019 14:01:37 -0400 [thread overview]
Message-ID: <feeae3ff-7985-7ad7-386e-d30d0a0a3ade@RedHat.com> (raw)
Hello,
I decided to make another release to address some
issues that were found with mountd in prior release.
The new rootdir nfs.conf configuration is include
as well as fixing some minor compile issues.
The tarballs can be found in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.4.1/
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.4.1
The change log is in
https://www.kernel.org/pub/linux/utils/nfs-utils/2.4.1/2.4.1-Changelog
or
http://sourceforge.net/projects/nfs/files/nfs-utils/2.4.1/
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:[~2019-06-10 18:01 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=feeae3ff-7985-7ad7-386e-d30d0a0a3ade@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).