From: Esben Haabendal <eha@doredevelopment.dk>
To: openembedded-devel@lists.openembedded.org
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>
Subject: Re: Bitbake task logging
Date: Sun, 02 Jan 2011 08:16:26 +0100 [thread overview]
Message-ID: <1293952586.18787.373.camel@eha> (raw)
In-Reply-To: <1293905677.17519.16909.camel@rex>
> e) I'm not 100% on this yet but I'm wondering if we should scrap
> stdout/stderr output to the UI console in debug mode, just make it clear
> where the output went on the console? If you ever have two tasks running
> the output is unreadable anyway.
Yes, stdout/stderr from two (or more) concurrent tasks are pretty
unreadable at best. But it could make sense to have a debug mode which
does output stdout/stderr to console, while disabling concurrent task
execution.
/Esben
next prev parent reply other threads:[~2011-01-02 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 18:14 Bitbake task logging Richard Purdie
2011-01-02 7:16 ` Esben Haabendal [this message]
2011-01-12 10:27 ` Aeschbacher, Fabrice
2011-01-12 12:35 ` Frans Meulenbroeks
2011-01-04 15:30 ` Chris Larson
2011-01-04 18:02 ` [Bitbake-dev] " Richard Purdie
2011-01-04 21:40 ` Yury Bushmelev
2011-01-05 0:45 ` Richard Purdie
2011-01-05 18:30 ` [Bitbake-dev] " Chris Larson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1293952586.18787.373.camel@eha \
--to=eha@doredevelopment.dk \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.