public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Petr Vorel <pvorel@suse.cz>,
	libtirpc <libtirpc-devel@lists.sourceforge.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: ANNOUNCE: libtirpc-1.2.6 released.
Date: Thu, 31 Oct 2024 22:27:02 -0400	[thread overview]
Message-ID: <9ef76fc7-e575-4229-867a-a6a56efabaec@redhat.com> (raw)
In-Reply-To: <91ef3508-d0a6-48db-adfc-4f7831fba74e@redhat.com>



On 10/29/24 7:20 AM, Petr Vorel wrote:
> From: Steve Dickson <steved@redhat.com>
> 
> Hi Steve,
> 
>> Hello,
>>
>> The 1.2.6 version of libtirpc has just been release.
> 
> I suppose this should be 1.3.6.
Yes.. My bad... Re-using old email... Sorry about that!

> 
>>
>> Minor release... a couple rpcbind config changes and
>> a few configuration changes for macOS.
>>
>> The tarball:
>> http://sourceforge.net/projects/libtirpc/files/libtirpc/1.2.6/ 
>> libtirpc-1.2.6.tar.bz2
> 
> https://sourceforge.net/projects/libtirpc/files/libtirpc/1.3.6/ 
> libtirpc-1.3.6.tar.bz2
True!

> 
>>
>> Release notes:
>> http://sourceforge.net/projects/libtirpc/files/libtirpc/1.2.6/ 
>> Release-1.2.6.txt
> 
> Could you please delete Release-1.2.6.txt
> https://sourceforge.net/projects/libtirpc/files/libtirpc/1.3.6/ 
> Release-1.2.6.txt
> 
> and upload:
> http://sourceforge.net/projects/libtirpc/files/libtirpc/1.3.6/ 
> Release-1.3.6.txt
Thanks for point this out...

steved.
> 
> Kind regards,
> Petr
> 
>>
>> The git tree is at:
>>     git://linux-nfs.org/~steved/libtirpc
>>
>>
>> steved.
>>
>>
> 


  parent reply	other threads:[~2024-11-01  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  8:15 ANNOUNCE: libtirpc-1.2.6 released Steve Dickson
2024-10-29 11:20 ` Petr Vorel
2024-11-01  2:27 ` Steve Dickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-09 18:06 Steve Dickson

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=9ef76fc7-e575-4229-867a-a6a56efabaec@redhat.com \
    --to=steved@redhat.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pvorel@suse.cz \
    /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