From: Gerd Hoerst <gerd@hoerst.net>
To: development@lists.ipfire.org
Subject: libusb upgrade 1.0.19 => 1.0.23
Date: Fri, 15 Nov 2019 15:38:53 +0100 [thread overview]
Message-ID: <4c1e0b9573dfd78de939802a8991c49e@hoerst.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
Hi !
Ipfire use since a long time libusb 1.0.19
Since i use o*scam on my ipfire i'm behind to have actual usbdrivers
regarding my USB Readers. (an also o*scam use it for compilation)
So i use long time 1.0.22 (actual 1.0.23 is in preparation) i created a
separate packacke to handle this because libusb is ussually shipped with
core update
How long is cycle in ipfire project to check for actual versions to be
integratd ?
Are you interested in a "hint" that libusb works that dev team can
integrate it ?
Please let me know..
Ciao Gerd
reply other threads:[~2019-11-15 14:38 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=4c1e0b9573dfd78de939802a8991c49e@hoerst.net \
--to=gerd@hoerst.net \
--cc=development@lists.ipfire.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