From: Colin Tuckley <colint@debian.org>
To: Hamlib Developers <hamlib-developer@lists.sourceforge.net>,
Debian Hams <debian-hams@lists.debian.org>,
Linux Hams <linux-hams@vger.kernel.org>,
Dave Freese <w1hkj@bellsouth.net>,
Ubuntu Hams Group <ubuntu-hams@lists.launchpad.net>
Subject: Re: Hamlib 3.0 release announcement
Date: Sat, 26 Mar 2016 12:43:39 +0000 [thread overview]
Message-ID: <56F683FB.3080702@debian.org> (raw)
In-Reply-To: <20150919142829.GS3787@n0nb.us>
On 19/09/15 15:28, Nate Bargmann wrote:
> The Hamlib Group is pleased to announce the release of Hamlib 3.0.
<big snip>
> TODO:
> Due to the apparent lack of a libusb package for Windows 64 bit, trial
> builds of the current Hamlib for W64 lack support for the USB backends.
> The project should transition these backends to the newer libusb 1.0
> series. Target: 3.1.
We have a Debian bug about this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810423
Is there any progress?
73, Colin G8TMV
next prev parent reply other threads:[~2016-03-26 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 14:28 Hamlib 3.0 release announcement Nate Bargmann
2016-03-26 12:43 ` Colin Tuckley [this message]
2016-03-26 13:26 ` Nate Bargmann
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=56F683FB.3080702@debian.org \
--to=colint@debian.org \
--cc=debian-hams@lists.debian.org \
--cc=hamlib-developer@lists.sourceforge.net \
--cc=linux-hams@vger.kernel.org \
--cc=ubuntu-hams@lists.launchpad.net \
--cc=w1hkj@bellsouth.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 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.