Hi everybody, I'd like to share one unrelated thing: I AM NOT subscribed to the libusbx related mailing lists and I AM NOT using it in my current development. I do appreciate the effort of all libusbx developers and I support them in their decisions. I hope once I will contribute something to it... but at this moment in time - I am subscribed to libusb development mailing list. Why I have to read about (IMHO quite childish) problems of a fork of libusb? I like how reasonable Pete and Hands are handling this so congratulations to them. But can you please remove 'old non-friendly libusb' thing from your CC's. Each maintainer/developer who will or would like to support libusb and libusbx should follow their thread and complain at their mailing list. Thanks, Jure Menart ----- Original Message ----- From: "Greg KH" <greg@xxxxxxxxx> To: "Kustaa Nyholm" <Kustaa.Nyholm@xxxxxxxxxxxx> Cc: libusb-devel@xxxxxxxxxxxxxxxxxxxxx, libusbx-devel@xxxxxxxxxxxxxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx, libusb-win32-devel@xxxxxxxxxxxxxxxxxxxxx Sent: Monday, 24 September, 2012 9:31:29 PM Subject: Re: [Libusbx-devel] libusbx-1.0.13 has been released On Mon, Sep 24, 2012 at 10:16:25PM +0300, Kustaa Nyholm wrote: > On 24.9.2012 21.47, "Greg KH" <greg@xxxxxxxxx> wrote: > > > >And if I'm going to be forced to change my program, and libusbx has now > >shown that they don't care about their public api, well, I might as well > >just rewrite it to remove that dependancy completly, as it's obvious > >they don't know how to treat their users. > > Really Greg, > > I think you are overreacting and talking through your hat. > > If you bothered to check the archives you'd see how much the developers > actually care about their users. Um, breaking existing applications is not indicative of that, don't you agree? > If you think rewriting to remove that dependency makes more sense > than applying a trivial fix Pete promised to deliver, go ahead, > especially if you think that is what *your* users will want. No one delivered any such "fix", all I got was a bunch of bug reports this morning from the distros saying that usbutils was suddenly broken. That shows that libusbx is really the problem here, and that maybe I shouldn't depend on it anymore. greg k-h ------------------------------------------------------------------------------ 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/ _______________________________________________ libusb-devel mailing list libusb-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/libusb-devel --- Disclaimer: --- This email and contents is for use only by the intended recipient. If you are not the individual or entity to whom it is addressed, you are hereby formally notified that any use, copying or distribution of this email and attachments, in whole or in part, is strictly prohibited. If you have received this email in error, please notify the sender and delete the message and attachment(s) from your system. Any views, opinions or information, expressed or contained in this email, are those of the sender and not necessarily reflect those of ESPROS Photonics AG. To help protect our environment, please avoid printing out this information unnecessarily. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
