On Sat, Apr 14, 2012 at 9:47 AM, Pete Batard <[email protected]> wrote: > On 2012.04.14 02:09, Xiaofan Chen wrote: >> [PATCH 16/37] Fix context memory leak in libusb_init() >> http://libusb.6.n5.nabble.com/PATCH-16-37-Fix-context-memory-leak-in-libusb-init-td9623.html >> >> [PATCH 15/37] log functions can be called before libusb_init >> http://libusb.6.n5.nabble.com/PATCH-15-37-log-functions-can-be-called-before-libusb-init-td8394.html >> (also not wanted Peter) >> http://libusb.6.n5.nabble.com/PATCH-08-11-log-functions-can-be-called-before-libusb-init-td5098365.html >> >> Actually both patches have some merits. Maybe we can discuss >> whether we should do something about this in libusbx-1.0.10 or >> 1.0.11. > > The time between RC and release is not exactly meant to introduce > patches that aren't seen as critical/showstoppers. Unlike what may seem > to be the case on libusb, the goal should be to have as few RCs as > possible... > > As such I will vote to only start looking at these patches only after > 1.0.10 has been released. But apart from that, anything is game, and old > patches that were rejected can indeed be proposed for integration in X.
1.0.10 has been released, shall we look at this topic now? -- Xiaofan ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
