On Sun, May 6, 2012 at 10:03 PM, Pete Batard <p...@akeo.ie> wrote: > On 2012.05.06 04:43, Xiaofan Chen wrote: >> Also now that libusbx fork is public, so I think it is not >> a problem to expose the original fork mailing list. > > Except we are going to be busy enough with reinstating HID, adding > topology, setting up gerrit and other stuff, which are all aimed to be > completed in under 4 weeks (looks unlikely right now) so, at least as > far as I'm concerned, I know I really won't have time to get back into > picking up libusb matters that aren't part of our roadmap for > at least a few more weeks. >
Actually it is perfectly okay to delay your involvement in the discussion. Last time we have a limited discussion in a small group so I think maybe it is a good idea to extend the discussion to a bigger group now that libusbx-devel is open to the public. Anyway, I guess your response will probably kill the discussion. So I will stop here. I should have sent this post to libusb-devel instead... -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
