> If the required changes to transmission are too huge for lucid, It's not really about the size of the change, it's about the unnecessary risk during an LTS freeze. (IMO.) If a serious bug is found in Transmission in the middle of April, I guarantee you'll find me here in Launchpad trying to push the fix into Lucid. :)
> [then] we have to change the strings from "KB/s" to "KiB/s". Even this change -- which is easy, safe, and (IMO) good -- would also make Transmission less compatible with most distributions. That's why I didn't do it six months ago, despite my personal preference to use IEC notation. And that's exactly why it's better to do this upstream. GNOME apps should not have to "take sides" in this tempest-in-a-teapot, nor should they each have to invent their own units helper functions. After the last years' worth of flamewars, you surely understand how many people feel strongly about this on both sides. It would be advantageous to have an upstream glib API to handle this issue to everyone's satisfaction. -- [UIFe] transmission measures bandwidth in KB/s instead of kB/s https://bugs.launchpad.net/bugs/538504 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
