From: Greg KH <greg@kroah.com>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: usbutils 0.86 release
Date: Mon, 17 Aug 2009 15:36:26 -0700 [thread overview]
Message-ID: <20090817223626.GA5826@kroah.com> (raw)
Here's the 0.86 release of usbutils.
There's a few minor fixups for the usb-devices script, as well as a
patch to help make fetching HID descriptors a bit more robust.
And a number of build configuration fixes as well.
The tarballs can be downloaded from sf.net at:
https://sourceforge.net/project/showfiles.php?group_id=3581
Or directly from kernel.org now:
http://www.kernel.org/pub/linux/utils/usb/usbutils/
We've switched over to using git for development now, which makes things
much easier than the old cvs tree. The tree can be found on both
kernel.org and github.com if you want to fork it and send us changes
easier:
http://git.kernel.org/?p=linux/kernel/git/gregkh/usbutils.git
http://github.com/gregkh/usbutils/tree/master
thanks,
greg k-h
-----------
Shortlog of changes since last release (0.84):
Aurelien Jarno (2):
usb-devices: move from /usr/sbin to /usr/bin
usb-devices: fix parsing of bcdDevice
Frans Pop (2):
usb-devices: harmonize class descriptions with usb/devices file
lsusb(8): make version variable and update date of last modification
Greg Kroah-Hartman (6):
update .gitignore to ignore .bz2 and .gz files
remove a lot of wireless driver names from usb.ids file
.gitignore update
build fix now that usb-devices man page has moved
usbutils 0.85 release
usbutils 0.86 release
Kay Sievers (2):
configure.ac: use AM_SILENT_RULES if available
usbutils.pc: place non arch dependent .pc file in /usr/share/pkgconfig/
Stéphane Chatty (1):
make HID devices a bit more robust
next reply other threads:[~2009-08-17 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 22:36 Greg KH [this message]
2009-08-17 22:42 ` usbutils 0.86 release Greg KH
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=20090817223626.GA5826@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox