ETAs for libusbx operability and first release?

Michael Plante michael.plante at gmail.com
Mon Feb 13 01:10:46 EST 2012


Segher Boessenkool wrote:
>> That's not going to happen.  If we pick up stuff that still needs
>> testing, we cannot release.


I would not call most of those "needs testing".  Most of those have been in
Pete Batard's repo for a very long time in one form or another.  I thought
part of the problem was a differing idea of what Peter thought "needs
testing" is and what we think "needs release" is?  But I'll grant that
you're probably just now seeing these for the first time, so you may not
realize how long most (not all) of them have been around.

536e424f -- essential to build lsusb on msvc6
c591a7cb -- nice, and only affects a few people
17ad642c -- essential, and only affects windows
8e15adcb -- essential, and only affects windows.  trivial to check.
ca097544 -- essential, and only affects windows.  no downside.
bb37939a -- nice, but you've personally reviewed it already and essentially
your only argument was that it was ugly.  Peter accepted it.
fa66c932 -- nice, and only affects windows.
e2807603 -- nice, and only affects a few people
f6ef0fca -- essential, and only affects windows.
c40f3df1 -- nice, and only affects a few people

("a few people" above specifically means a subset of windows, i.e., msvc6.)

If you want me to make you a branch with just these commits (I'll pick a
fairly vague name so Peter won't guess what I'm doing), please make me a
list of categories above that you are interested in and I will do so.
Please also give me a timeline.  This weekend is over, so hopefully next
weekend is acceptable.  It's doubtful I can do much during the week.

Thanks,
Michael




More information about the libusbx mailing list