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.3 released.
Date: Mon, 31 Mar 2025 11:57:42 -0400 [thread overview]
Message-ID: <5393a1f8-898e-4e1d-b516-7d0070086655@redhat.com> (raw)
In-Reply-To: <Z-oRa3cF97JCGkVo@lorien.valinor.li>
On 3/30/25 11:52 PM, Salvatore Bonaccorso wrote:
> Hi Steve,
>
> On Sun, Mar 30, 2025 at 03:37:33PM -0400, Steve Dickson wrote:
>> Hello,
>>
>> The release has a number changes in time for
>> the upcoming Spring Bakeathon (May 12-16):
>>
>> * A number of man pages updates
>> * Bug fixes for nfscld and gssd
>> * New argument to nfsdctl as well as some bug fixes
>> * Bug fixes to mountstats and nfsiostat
>> * Updates to rpcctl
>>
>> As well as miscellaneous other bug fixes see
>> the Changelog for details.
>>
>> The tarballs can be found in
>> https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.3/
>> or
>> http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.3
>>
>> The change log is in
>> https://www.kernel.org/pub/linux/utils/nfs-utils/2.8.3/2.8.3-Changelog
>> or
>> http://sourceforge.net/projects/nfs/files/nfs-utils/2.8.2/2.8.3-Changelog
>>
>>
>> The git tree is at:
>> git://linux-nfs.org/~steved/nfs-utils
>>
>> Please send comments/bugs to linux-nfs@vger.kernel.org
>
> Thansk for this new release!
>
> Noticed that the nfs-utils-2-8-3 and release commit is not yet in
> https://git.linux-nfs.org/?p=steved/nfs-utils.git . Could you push
> those as well?
Done!! My bad... sorry about that... Can you say brain fart :-)
steved.
>
> Regards,
> Salvatore
>
prev parent reply other threads:[~2025-03-31 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 19:37 ANNOUNCE: nfs-utils-2.8.3 released Steve Dickson
2025-03-31 3:52 ` Salvatore Bonaccorso
2025-03-31 15:57 ` 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=5393a1f8-898e-4e1d-b516-7d0070086655@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