On 2013.06.20 12:11, Hans de Goede wrote: > Done (more or less, see git).
Even with the dual set of patches, I'm still not sure we wouldn't want to at least print a debug message if we find out that libusb_cancel_transfer(...) failed. But I guess we can go with the current proposal. On a side note, I'd very much prefer a cool-off period of at least one day between the last non-minor commit being pushed and RC (the patches you pushed against sync.c don't look that minor to me). I know we're all in a hurry to get RC off the ground, but I've had too many bad surprises from seemingly innocuous fixes breaking Windows, and I can't help getting nervous seeing something flagged as RC before it has been tested on all the Windows platforms. This being said, I have just re-run the usual set of VS2012+Code Analysis, MinGW-Clang, cygwin, WDK (also threw in MinGW-w64 for good measure) and things look OK as far as compilation is concerned. Regards, /Pete ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
