Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default
Paul Sokolovsky
Hello Luiz,
toggle quoted messageShow quoted text
On Fri, 15 Sep 2017 12:26:10 +0300
Luiz Augusto von Dentz <luiz.dentz@...> wrote: [] Well, when someone comes by and says "You're doing great, but we won'tWe should think beyond that, we should think why, 8 months after theWhen you use a presentation which says: use your stuff and can't even tell where we will be able to" (and that's arguably summarizes that presentation), I'd spend less time on being flattered by a polite conversation starter, and would spend more time on 2nd part of the message ;-). I understand it can be frustrating to not have proper logs when facingIt's true that Zephyr development moves fast overall, and yet some things are vice-versa pretty slow, for example here we, at version 1.9, discuss whether it makes sense to report error messages or not. [] Note, this can all be achieved without a wall of text complainingYeah, sorry about that. I mentioned that I "sent probes" on this before, and quite anticipated the possible response ("let's not change things, everything works well as it is"). So, I appreciate that everyone agrees we can change in logging *something*, I'm just trying to convey that we should change a bunch of stuff consistently to make a real difference. Anyway, I'm off to patches on this stuff. [] -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
|
|