From: Steve Dickson <SteveD@redhat.com>
To: libtirpc <libtirpc-devel@lists.sourceforge.net>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: ANNOUNCE: libtirpc-0.2.4 released.
Date: Mon, 09 Dec 2013 16:25:45 -0500 [thread overview]
Message-ID: <52A63559.4020903@RedHat.com> (raw)
Hello,
The 0.2.4 version of libtirpc has just been release. This
is basically a bug fix release. The release notes detailing
the bug fixes are at:
http://sourceforge.net/projects/libtirpc/files/libtirpc/0.2.4/ReleaseNotes.txt
The tarball can be found at:
http://sourceforge.net/projects/libtirpc/files/libtirpc/0.2.4/libtirpc-0.2.3.tar.bz2
The git tree is at:
git://git.infradead.org/~steved/libtirpc.git
steved.
reply other threads:[~2013-12-09 21:24 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=52A63559.4020903@RedHat.com \
--to=steved@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.