Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: ANNOUNCE: nfs-utils-2.8.5 released.
Date: Sat, 14 Feb 2026 13:28:56 -0500	[thread overview]
Message-ID: <dfd0d59a-a0ca-484d-981a-55cac8d89717@redhat.com> (raw)
In-Reply-To: <aYlpcPkq_glykQvJ@eldamar.lan>



On 2/8/26 11:58 PM, Salvatore Bonaccorso wrote:
> Hi Steve,
> 
> On Mon, Feb 02, 2026 at 06:45:30AM -0500, Steve Dickson wrote:
>> Hello,
>>
>> This release contains the following:
>>
>>      * Man page corrections
>>      * min-threads parameter added to nfsdctl.
>>      * systemd updates to rpc-statd-notify.
>>      * blkmapd not built by default (--enable-blkmapd to re-enable)
>>      * A number of other bug fixes.
>>
>> The tarballs can be found in
>>    https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.5/
>> or
>>    http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.5
>>
>> The change log is in
>>     https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.5/2.8.5-Changelog
>> or
>>   http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.4/2.8.5-Changelog
>>
>>
>> The git tree is at:
>>     git://linux-nfs.org/~steved/nfs-utils
> 
> While 2.8.5 was released, I do not see yet a release commit and tag in
> the git repository, is this correct?
Sorry I was traveling and forgot do the push... It is there now.

steved.

> 
> Regards,
> Salvatore
> 


      reply	other threads:[~2026-02-14 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 11:45 ANNOUNCE: nfs-utils-2.8.5 released Steve Dickson
2026-02-09  4:58 ` Salvatore Bonaccorso
2026-02-14 18:28   ` 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=dfd0d59a-a0ca-484d-981a-55cac8d89717@redhat.com \
    --to=steved@redhat.com \
    --cc=carnil@debian.org \
    --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