Alexandre Ratchov, 22 Nov 2014 11:22:
> IMHO we should keep the message because upstream developpers have
> added it for a reason. We could add a second message right after
> the sio_stop() call to appreciate the time sio_stop() takes and if
> this is annoying find a solution.
> 
> In other words, let's fix the "bug" and let upstream remove the
> warning

upstream is very open to patches and will
commit them sooner than the port itself :)

-f
-- 
you don't have to be a cannibal to get fed up with people.


Reply via email to