From: Greg KH <greg@kroah.com>
To: Valdis.Kletnieks@vt.edu
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Mike Frysinger <vapier.adi@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: usbutils 0.81 release
Date: Wed, 29 Apr 2009 14:56:23 -0700 [thread overview]
Message-ID: <20090429215623.GA27319@kroah.com> (raw)
In-Reply-To: <44275.1241041373@turing-police.cc.vt.edu>
On Wed, Apr 29, 2009 at 05:42:53PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 29 Apr 2009 12:23:09 PDT, Greg KH said:
>
> > Distros ship uppdate-usbids.sh, like they do the same for the pci ids
> > file. And you can consider the usb.ids file a "config file" :)
>
> So my Fedora Rawhide box still has usbutils 0.73. I go snarf usbutils 0.81
> from SourceForge and I find:
>
> [~/src/usbutils-0.81] ls
> AUTHORS Makefile.am aclocal.m4 depcomp list.h missing usbmisc.c
> COPYING Makefile.in config.h.in devtree.c lsusb-t.c names.c usbmisc.h
> ChangeLog NEWS configure devtree.h lsusb.8 names.h
> INSTALL README configure.ac install-sh lsusb.c usb.ids
> [~/src/usbutils-0.81] grep update-usb *
> ChangeLog: * update-usbids.sh: add "-q" (quiet) option for cron jobs;
> ChangeLog: * update-usbids.sh: add, based on update-pciids.sh
> [~/src/usbutils-0.81]
>
> So it's not in the tarball, and it's apparently not created by the Makefile.
>
> So where is it?
As was pointed out by Mike, a bug in the Makefile prevented it from
being added to the tarball.
If youreally want it, you can grab it from the git tree, or wait a day
or so for me to implement Mike's changes he so nicely sent me, so I can
do a new release.
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-29 21:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 19:35 usbutils 0.81 release Greg KH
2009-04-27 20:48 ` Alan Stern
2009-04-27 21:00 ` Greg KH
2009-04-27 21:21 ` Alan Stern
2009-04-27 21:36 ` Kay Sievers
2009-04-29 14:23 ` Benny Amorsen
2009-04-29 15:51 ` Alan Stern
2009-04-29 17:27 ` Mike Frysinger
2009-04-29 17:42 ` Greg KH
2009-04-29 20:23 ` Alan Stern
2009-04-27 21:07 ` Kay Sievers
2009-04-27 21:54 ` Alan Stern
2009-04-27 22:02 ` Kay Sievers
2009-04-29 17:53 ` Mike Frysinger
2009-04-29 18:07 ` Greg KH
2009-04-29 18:17 ` Mike Frysinger
2009-04-29 18:30 ` Greg KH
2009-04-29 23:38 ` Mike Frysinger
2009-04-30 0:45 ` Kay Sievers
2009-04-30 1:48 ` Mike Frysinger
2009-04-30 1:54 ` Kay Sievers
2009-04-30 1:58 ` Mike Frysinger
2009-04-29 18:59 ` Kay Sievers
2009-04-29 19:18 ` Henrique de Moraes Holschuh
2009-04-29 19:26 ` Greg KH
2009-04-29 19:44 ` Kay Sievers
2009-04-29 19:27 ` Kay Sievers
2009-04-29 19:50 ` Henrique de Moraes Holschuh
2009-04-29 19:55 ` Kay Sievers
2009-04-29 20:00 ` Henrique de Moraes Holschuh
2009-04-29 20:39 ` Kay Sievers
2009-04-30 6:31 ` Bjørn Mork
2009-04-29 19:23 ` Greg KH
2009-04-29 21:42 ` Valdis.Kletnieks
2009-04-29 21:56 ` Greg KH [this message]
2009-04-29 22:19 ` Valdis.Kletnieks
2009-04-30 1:48 ` Kay Sievers
2009-04-30 1:56 ` Mike Frysinger
2009-04-30 2:06 ` Kay Sievers
2009-04-30 2:13 ` Mike Frysinger
2009-04-30 4:54 ` Greg KH
2009-04-29 21:57 ` Kay Sievers
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=20090429215623.GA27319@kroah.com \
--to=greg@kroah.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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