ETAs for libusbx operability and first release?

[Pete Batard]

Once again, this is super-annoying:

I used a (was: XYZ) header, but still got bounced back...
Oh, and I'm gonna add some irrelevant text from the existing thread at 
the end, in the hope that this one won't bounce either.

Regards,

/Pete

On 2012.01.31 15:54, libusbx-bounces at lists.infradead.org wrote:
 > Your mail to 'libusbx' with the subject
 >
 >      HID re-integration (was: ETAs for libusbx operability and first
 > release?)
 >
 > Is being held until the list moderator can review it for approval.
 >
 > The reason it is being held:
 >
 >      Message has a suspicious header
 >
 > Either the message will get posted to the list, or you will receive
 > notification of the moderator's decision.  If you would like to cancel
 > this posting, please visit the following URL:
 >
 > 
http://lists.infradead.org/mailman/confirm/libusbx/5ad62c823a43ac8981d2bc2bc9bf948b56463317
 >

[IRRELEVANT BEGINS HERE]
On 2012.01.31 02:11, Xiaofan Chen wrote:
 > On Tue, Jan 31, 2012 at 1:08 AM, Pete Batard<pete at akeo.ie>  wrote:
 >> On 2012.01.30 16:46, Segher Boessenkool wrote:
 >>>>
 >>>> Well, my problem here is that I've accumulated quite a few things that
 >>>> I'd like to push,
 >>>
 >>> Yeah. Lucky for you libusb hasn't diverged much in the many months
 >>> you've been waiting.
 >>
 >> Actually it did. The removal of HID was a major PITA, since hotplug was
 >> based on code that had HID. I also haven't updated the hotplug 
branch for
 >> months, so there might be surprises.
 >
 > I would like to have HID back. HIDAPI is good. However, it will probably
 > not have hotplug feature anytime soon. And libusb-1.0 with Windows
 > HID backend should still be good for quite some users. And when it
 > gains hotplug feature, then it has at least one advantage against HIDAPI.
 >
 > Nathan was against the idea of an native HID backend for Mac OS X
 > so probably it will not happen for Mac OS X.
 >
 > But I understand that this should be post 1.0.9 release. So we can
 > discuss this after 1.0.9 release.
 >