On 2012.04.25 08:21, Peter Stuge wrote: > libusb_get_version() is an API addition in the libusb.git codebase, > like it is in the libusbx.git codebase.
As you should know, the API addition also includes the structure associated with the function call, so you should be careful to consider both if you carry out the change on your side. >> without any discussion at all! > > Given the libusbx announcement I guess you may understand that there > didn't seem to be much to discuss. The libusbx announcement shouldn't detract you from your duties as a maintainer towards libusb users, which includes entitling them to review and comment of API changes. Whether you want to discuss with us in one thing. Whether you want to discuss with libusb users, which is what this point is all about, with regards to changes that very much impact them, is another. Now, with regards to what libusbx will do to sort the current incompatibility, and unless someone has further objections (or would prefer a different string), I should push a commit later on today that adds the static string "unused - please use the nano" to the libusbx version struct. Regards, /Pete ------------------------------------------------------------------------------ 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
