[bitbake-devel] bitbake/logging: Overhaul internal logging process

[Tom Rini]

On Fri, Aug 12, 2011 at 7:25 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> At the moment it bugs me a lot that we only have one effective logging
> level for bitbake, despite the logging module having provision to do
> more advanced things. This patch:
>
> * Changes the core log level to the lowest level we have messages of
>  (DEBUG-2) so messages always flow through the core logger
> * Allows build.py's task logging code to log all the output regardless
>  of what output is on the console and sets this so log files now
>  always contain debug level messages even if these don't appear
>  on the console
> * Moves the verbose/debug/debug-domains code to be a UI side setting
> * Adds a filter to the UI to only print the user requested output.

Can we also get a way (or big enough log level) to get timestamps thrown in?

-- 
Tom