On Tue, Aug 28, 2012 at 5:55 AM, Pete Batard <p...@akeo.ie> wrote: >>>> libusbx: info [get_interface_details_filter] assigned libusb0 symbolic >>>> link \\.\ >>>> libusb0-0001 >>> >>> Mmm, maybe we should set that info message to debug? What do you think? >>> Not the message is that informational after all... >> >> Yes I agree. > > OK, I'll push that change later on. > > Another info message that we might also want to consider setting as > debug is the "libusbK DLL is not available, will use native WinUSB" one > might get during init. > > Personally, I think the message might be worth being flagged as info, so > that we tell users whether the K DLL is involved at all when dealing > with WinUSB, but on the other hand, it may not be that big a deal, as we > would easily get that info when we ask for debug info anyway. > What would your preference be on that one?
I think it is okay to flag the message as info. -- 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
