Le 10/03/2013 15:54, Thomas Preud'homme a écrit :
This has been submitted upstream on
https://sourceforge.net/tracker/?func=detail&aid=3607521&group_id=250683&at
id=1126467 I just hope that Debian packagers are faster than dspam main
development team :)
The general rule in Debian is to not include patches which where not included
upstream, unless it's Debian-specific or urgent (think security fixes) or very
important (data loss). I don't think this change qualify for one of these
exceptions but maybe I don't realize
how big is the problem.
If using select is such a problem that it should be fixed right away, can you
explain me why because it doesn't look so important to me.
Thanks for your bug report and for forwarding the bug upstream by yourself.
Best regards,
Thomas
If it's the rule, then OK. This is not really important as security
fixes or data losses. It's just part of "useless wakeups" hunt. I try to
eradicate those behaviour, in order to have a really efficient server:
less wakeups, less wasted watts. Or more services at the same time.
So, unfortunately for me, I have to admit than it is not important
enough to be included only in Debian. I'll have to wait for inclusion in
upstream then.
Thanks for your answer!
Adrien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
