Hi there, I'm preparing the 2.0.3-pre2 release. I've decided, as an exception (the second with the ones for 2.0.2, but hey, nut has a lot of late to resorb) to merge the USB improvements from the CVS Development branch. That means that the updated newhidups, as well as tripplite_usb and bcmxcp_usb if these are fine. To Charles and Wolfgang: any comments, objections, last things to be done, ...? However, there will be no concessions to stability. So once 2.0.3-pre2 is out, I'll call for a massive test and feedback. Arnaud <http://arnaud.quette.free.fr/> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20051001/a9ff8f7a/attachment.htm
On 10/1/05, Arnaud Quette <aquette.dev@gmail.com> wrote:> That means that the updated newhidups, as well as tripplite_usbHmm, I guess I haven't merged the Tripp_Lite_Omni branch back into the Development branch. It would probably be good for me to do that before you backport changes to 2.0.3-pre2. (The tripplite_usb code currently on the Development branch isn't very far along.) I'll start working on that. -- - Charles Lepple
On 10/1/05, Arnaud Quette <aquette.dev@gmail.com> wrote:> That means that the updated newhidups, as well as tripplite_usb > and bcmxcp_usb if these are fine. > To Charles and Wolfgang: any comments, objections, last things > to be done, ...?Wolfgang, Should the bcmxcp_usb driver be backported to testing? I don't mind committing it, but I don't have any hardware to test. -- - Charles Lepple