From: Nate Bargmann <n0nb@bluevalley.net>
To: Stephane Fillod <f8cfe@free.fr>,
Hamlib developers <hamlib-developer@lists.sourceforge.net>,
Linux HAMs <Linux-hams@vger.kernel.org>
Subject: Re: [ANN] Hamlib 1.2.7.1 released
Date: Sat, 12 Apr 2008 07:47:00 -0500 [thread overview]
Message-ID: <200804120747.00381.n0nb@bluevalley.net> (raw)
In-Reply-To: <20080412112752.GQ6021@charybde.local>
On Saturday 12 April 2008 06:27:52 Stephane Fillod wrote:
> Good news everyone!
>
> Hamlib-1.2.7.1 has been released.
Thanks, Stephane.
73, de Nate >>
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-12 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 11:27 [ANN] Hamlib 1.2.7.1 released Stephane Fillod
2008-04-12 12:47 ` Nate Bargmann [this message]
2008-04-15 1:26 ` William Liporace
2008-04-15 1:36 ` Berndt Josef Wulf
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=200804120747.00381.n0nb@bluevalley.net \
--to=n0nb@bluevalley.net \
--cc=Linux-hams@vger.kernel.org \
--cc=f8cfe@free.fr \
--cc=hamlib-developer@lists.sourceforge.net \
/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